browser-harness vs io.github.browserbase/mcp-server-browserbase
browser-harness is a plugin bundle for AI coding tools published by browser-use. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.browserbase/mcp-server-browserbase is an MCP server published by browserbase. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-13. 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 |  io.github.browserbase/mcp-server-browserbase | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.0 Forks (GitHub): 1 804 Stars (GitHub): 18 403 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.1 Downloads/month (npm): 18 800 Downloads/week (npm): 3 122 Forks (GitHub): 372 Stars (GitHub): 3 402 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:f90cb76e34ba Forks (GitHub): 372 Pulls (Docker Hub): 38 058 Stars (Docker Hub): 1 Stars (GitHub): 3 402 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 | browser-harness | io.github.browserbase/mcp-server-browserbase |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 18 403 (better) | 3 402 (worse) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 38 058 |
| Forks (GitHub) (differs) | 1 804 (better) | 372 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | stdio, Streamable HTTP |
| Tools it declares (differs) | Not published | 6 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 2 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/browser-use/browser-harness | github.com/browserbase/mcp-server-browserbase |
| 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 | not checked yet |
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
browser-harness
Open-source browser agent driven via CDP — direct browser control, 79K stars, YC W25. browser-harness gives Claude Code direct, low-level control of a real Chrome browser via the Chrome DevTools Protocol. Coordinate-level clicks pass through iframes, shadow DOM, and cross-origin frames at the compositor level — no selector hunting, no Playwright wrappers. Connects to a long-running Browser Use Cloud or local browser session, so logins persist across runs. Highlights: - Screenshot-first workflow: capture → read pixel → click_at_xy → re-capture to verify - Bulk HTTP fetch helper for static pages (no browser overhead) - Raw CDP escape hatch for anything helpers don’t cover - Interaction skills for dialogs, dropdowns, iframes, shadow DOM, file uploads, cross-origin frames - Remote browsers via Browser Use Cloud — share a live URL with a human when login/CAPTCHA blocks the agent
io.github.browserbase/mcp-server-browserbase
MCP server for AI web browser automation using Browserbase and Stagehand
How to run each
browser-harness
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.browserbase/mcp-server-browserbase As a local MCP server: npm package
claude mcp add --env "BROWSERBASE_API_KEY=<YOUR_BROWSERBASE_API_KEY>" --env "BROWSERBASE_PROJECT_ID=<YOUR_BROWSERBASE_PROJECT_ID>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --transport stdio mcp-server-browserbase -- npx -y @browserbasehq/mcp-server-browserbaseRequires: BROWSERBASE_API_KEY (secret), BROWSERBASE_PROJECT_ID, GEMINI_API_KEY (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 browser-harness publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of browser-harness publish no settings it asks for, so we do not compare settings.
What it can do: browser-harness · What it can do: io.github.browserbase/mcp-server-browserbase · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.