io.github.browserbase/mcp-server-browserbase vs Mobdev
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). Mobdev is an MCP server published by niklas-schmidt-dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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 | ||
|---|---|---|
| Official MCP Registry | 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 |
Listed Version: 0.2.54 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:f90cb76e34ba Forks (GitHub): 372 Pulls (Docker Hub): 38 058 Stars (Docker Hub): 1 Stars (GitHub): 3 402 Not marked · First seen |
Not listed |
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 | io.github.browserbase/mcp-server-browserbase | Mobdev |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 402 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 38 058 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 372 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | Not stated |
| Transport (differs) | stdio, Streamable HTTP | Not stated |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/browserbase/mcp-server-browserbase | github.com/niklas-schmidt-dev/mobdev |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
io.github.browserbase/mcp-server-browserbase
MCP server for AI web browser automation using Browserbase and Stagehand
Mobdev
Mac app that lets AI agents drive iPhones, iOS simulators and Android: tap, type, install, logs.
How to run each
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-browserbase
Requires: BROWSERBASE_API_KEY (secret), BROWSERBASE_PROJECT_ID, GEMINI_API_KEY (secret)
Mobdev
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 Mobdev publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Mobdev publish no settings it asks for, so we do not compare settings.
What it can do: io.github.browserbase/mcp-server-browserbase · What it can do: Mobdev · 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.