Ext Ops Panel
Open dashboard
Comparison

Chrome DevTools MCP vs io.github.browserbase/mcp-server-browserbase

Chrome DevTools MCP is an MCP server published by ChromeDevTools. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Copilot CLI: github/awesome-copilot, Community GitHub marketplaces, 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-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

Where each is published
MarketplaceChrome DevTools MCPio.github.browserbase/mcp-server-browserbase
Official MCP Registry Listed
Version: 1.10.1
Downloads/month (npm): 7 493 150
Downloads/week (npm): 1 060 392
Forks (GitHub): 6 431
Stars (GitHub): 53 447
Not marked · First seen
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
Claude Code: claude-plugins-official Listed
Version: 1.9.0
Forks (GitHub): 6 431
Stars (GitHub): 53 447
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.1
Forks (GitHub): 6 431
Stars (GitHub): 53 447
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 1.6.0
Forks (GitHub): 6 431
Stars (GitHub): 53 447
Not marked · First seen
Not listed
Docker MCP Catalog Not listed Listed
Version: sha256:f90cb76e34ba
Forks (GitHub): 372
Pulls (Docker Hub): 38 066
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

Chrome DevTools MCP vs io.github.browserbase/mcp-server-browserbase
FactChrome DevTools MCPio.github.browserbase/mcp-server-browserbase
Marketplaces that list it (differs)5 (better)2 (worse)
Stars (GitHub) (differs)53 447 (better)3 402 (worse)
Pulls (Docker Hub) (differs)No figure on Docker Hub38 066
Forks (GitHub) (differs)6 431 (better)372 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (chrome-devtools-mcp)Remote server or your machine
Transport (differs)stdiostdio, Streamable HTTP
Tools it declares (differs)Not published6
Environment variables it asks for (differs)Not published3, secrets among them: 2
Parts of the bundle (differs)8Not a bundle
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/chromedevtools/chrome-devtools-mcpgithub.com/browserbase/mcp-server-browserbase
Changes in the last 7 days (differs)90
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot 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

Chrome DevTools MCP

In its own words, on Official MCP Registry:

MCP server for Chrome DevTools

io.github.browserbase/mcp-server-browserbase

In its own words, on Official MCP Registry:

MCP server for AI web browser automation using Browserbase and Stagehand

How to run each

Chrome DevTools MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio chrome-devtools-mcp -- npx -y chrome-devtools-mcp

io.github.browserbase/mcp-server-browserbase As a local MCP server: npm package

Claude Code
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-browserbase

Requires: 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 Chrome DevTools MCP publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Chrome DevTools MCP publish no settings it asks for, so we do not compare settings.

What it can do: Chrome DevTools MCP · What it can do: io.github.browserbase/mcp-server-browserbase · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built