Ext Ops Panel
Open dashboard
Comparison

Hyperbrowser vs web-ctl

Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). web-ctl is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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

Where each is published
MarketplaceHyperbrowserweb-ctl
Docker MCP Catalog Listed
Version: sha256:11ed80138c33
Forks (GitHub): 75
Pulls (Docker Hub): 41 144
Stars (Docker Hub): 3
Stars (GitHub): 789
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: e00f409
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

Hyperbrowser vs web-ctl
FactHyperbrowserweb-ctl
Marketplaces that list it11
Stars (GitHub) (differs)789No figure on GitHub
Pulls (Docker Hub) (differs)41 144No figure on Docker Hub
Forks (GitHub) (differs)75No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/hyperbrowser)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)10Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/hyperbrowserai/mcpgithub.com/agent-sh/web-ctl
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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

In its own words, on Docker MCP Catalog:

A MCP server implementation for hyperbrowser.

web-ctl

In its own words, on Claude Code: claude-plugins-community:

Browser automation toolkit for AI agents — navigate, authenticate, and interact with web pages through a single CLI. Agents drive headless browsers to fill forms, click buttons, read content, and capture screenshots; when login or CAPTCHA is required, the browser opens for the human, the human completes auth, and control returns to headless mode (auth handoff). Persistent sessions survive across CLI invocations so the agent doesn't need to log in repeatedly. Built-in prompt-injection defense for content read from pages. Designed for tasks where the agent needs to interact with a real web app — testing flows, scraping behind a login, automating internal dashboards.

How to run each

Hyperbrowser As a local MCP server: Docker image

Claude Code
claude mcp add --env "HYPERBROWSER_API_KEY=<YOUR_HYPERBROWSER_API_KEY>" --transport stdio hyperbrowser -- docker run -i --rm -e HYPERBROWSER_API_KEY mcp/hyperbrowser

Requires: HYPERBROWSER_API_KEY (secret)

web-ctl

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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-ctl publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of web-ctl publish no settings it asks for, so we do not compare settings.

What it can do: Hyperbrowser · What it can do: web-ctl · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built