Mirrors vs io.github.browserbase/mcp-server-browserbase
Mirrors is an MCP server published by runmirrors.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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-16. 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 |  Mirrors |  io.github.browserbase/mcp-server-browserbase |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.1.1 Downloads/month (npm): 19 182 Downloads/week (npm): 2 969 Forks (GitHub): 371 Stars (GitHub): 3 399 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:f90cb76e34ba Forks (GitHub): 371 Pulls (Docker Hub): 38 088 Stars (Docker Hub): 1 Stars (GitHub): 3 399 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 | Mirrors | io.github.browserbase/mcp-server-browserbase |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 3 399 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 38 088 |
| Forks (GitHub) (differs) | 0 (worse) | 371 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.runmirrors.com/mcp) | Remote server or your machine |
| Transport (differs) | Streamable HTTP | stdio, Streamable HTTP |
| Tools it declares (differs) | Not published | 6 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 2 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/ai-singhal/mirrorkit-go | 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) | Not responding since 2026-10-14 | Answered with HTTP 404 (24 h 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
Mirrors
AI agent testing: replay real sessions against a rebuilt staging environment to catch regressions.
io.github.browserbase/mcp-server-browserbase
MCP server for AI web browser automation using Browserbase and Stagehand
How to run each
Mirrors As a remote MCP server
claude mcp add --transport http mirrors https://api.runmirrors.com/mcpio.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.
Neither endpoint responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of Mirrors publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Mirrors publish no settings it asks for, so we do not compare settings.
What it can do: Mirrors · 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 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.