Hyperbrowser vs WebRun Browser Automation
Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). WebRun Browser Automation is an MCP server published by webrun.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 184 Stars (Docker Hub): 3 Stars (GitHub): 789 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 No figure published 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 | WebRun Browser Automation |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 789 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 41 184 | 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) | Remote server (api.webrun.ai/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hyperbrowserai/mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
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.
WebRun Browser Automation
Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.
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)
WebRun Browser Automation As a remote MCP server
claude mcp add --transport http webrun https://api.webrun.ai/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only WebRun Browser Automation has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of WebRun Browser Automation publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of WebRun Browser Automation publish no settings it asks for, so we do not compare settings.
What it can do: Hyperbrowser · What it can do: WebRun Browser Automation · 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.