Ext Ops Panel
Open dashboard
Comparison

upAPI vs io.github.browserbase/mcp-server-browserbase

upAPI is an MCP server published by DevinoSolutions. 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-15. 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
MarketplaceupAPIio.github.browserbase/mcp-server-browserbase
Official MCP Registry Listed
Version: 0.2.0
Downloads/month (npm): 1 088
Downloads/week (npm): 254
Forks (GitHub): 0
Stars (GitHub): 0
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 400
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:f90cb76e34ba
Forks (GitHub): 372
Pulls (Docker Hub): 38 075
Stars (Docker Hub): 1
Stars (GitHub): 3 400
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

upAPI vs io.github.browserbase/mcp-server-browserbase
FactupAPIio.github.browserbase/mcp-server-browserbase
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)3 400 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub38 075
Forks (GitHub) (differs)0 (worse)372 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (app.upapi.io/api/mcp)Remote server or your machine
Transport (differs)Streamable HTTPstdio, Streamable HTTP
Tools it declares (differs)Not published6
Environment variables it asks for (differs)2, secrets among them: 13, secrets among them: 2
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/devinosolutions/upapi-mcpgithub.com/browserbase/mcp-server-browserbase
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 39 h ago, requires a keynot 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

upAPI

In its own words, on Official MCP Registry:

All public upAPI operations as MCP tools: web scraping, search, screenshots, PDF, OCR and more.

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

upAPI As a remote MCP server

Claude Code
claude mcp add --transport http upapi-mcp https://app.upapi.io/api/mcp

Requires: UPAPI_API_KEY (secret)

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.

Only upAPI has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of upAPI publish no list of tools, so we do not compare tools.

Settings each asks for

Only upAPI asks for

  • UPAPI_API_KEY (secret)
  • UPAPI_TOOL_MODE

Only io.github.browserbase/mcp-server-browserbase asks for

  • BROWSERBASE_API_KEY (secret)
  • BROWSERBASE_PROJECT_ID (secret)
  • GEMINI_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: upAPI · 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.

Where the data comes from: how the catalog is built