Hyperbrowser vs Web Task
Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). Web Task is an MCP server published by jojo-labs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Hyperbrowser | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:11ed80138c33 Forks (GitHub): 75 Pulls (Docker Hub): 41 173 Stars (Docker Hub): 3 Stars (GitHub): 789 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.10.1 Downloads/month (npm): 320 Downloads/week (npm): 83 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Hyperbrowser | Web Task |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 789 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 41 173 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 75 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/hyperbrowser) | On your machine (web-task-api) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 16, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hyperbrowserai/mcp | github.com/jojo-labs/web-task-api |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Hyperbrowser
A MCP server implementation for hyperbrowser.
Web Task
Browser tasks, sessions, and recipes for MCP and HTTP automation.
How to run each
Hyperbrowser As a local MCP server: Docker image
claude mcp add --env "HYPERBROWSER_API_KEY=<YOUR_HYPERBROWSER_API_KEY>" --transport stdio hyperbrowser -- docker run -i --rm -e HYPERBROWSER_API_KEY mcp/hyperbrowserRequires: HYPERBROWSER_API_KEY (secret)
Web Task As a local MCP server: npm package
claude mcp add --env "CLIPROXY_AUTH_TOKEN=<YOUR_CLIPROXY_AUTH_TOKEN>" --transport stdio web-task-api -- npx -y web-task-apiRequires: CLIPROXY_AUTH_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Web Task publish no list of tools, so we do not compare tools.
Settings each asks for
Only Hyperbrowser asks for
HYPERBROWSER_API_KEY (secret)
Only Web Task asks for
BROWSER_CHANNELBROWSER_USER_DATA_DIRCLIPROXY_AUTH_TOKEN (secret)CLIPROXY_BASE_URLCLIPROXY_MODELHEADLESSOPENCODE_BASE_URLOPENCODE_MODELWEB_TASK_API_DATA_DIRWEB_TASK_API_MODELWEB_TASK_API_PI_MODELWEB_TASK_API_PI_URL
Show the remaining 4
WEB_TASK_API_PI_VARIANTWEB_TASK_API_RECIPES_DIRWEB_TASK_API_TEMP_DIRWEB_TASK_API_VARIANT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Hyperbrowser · What it can do: Web Task · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.