Ext Ops Panel
Open dashboard
Comparison

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

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). vibatchium is an MCP server published by trueoriginlabs. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
Marketplaceio.github.browserbase/mcp-server-browserbasevibatchium
Official MCP Registry 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
Listed
Version: 0.20.0
Downloads/month (PyPI): 548
Downloads/week (PyPI): 262
Forks (GitHub): 1
Stars (GitHub): 7
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:f90cb76e34ba
Forks (GitHub): 371
Pulls (Docker Hub): 38 078
Stars (Docker Hub): 1
Stars (GitHub): 3 399
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

io.github.browserbase/mcp-server-browserbase vs vibatchium
Factio.github.browserbase/mcp-server-browserbasevibatchium
Marketplaces that list it22
Stars (GitHub) (differs)3 399 (better)7 (worse)
Pulls (Docker Hub) (differs)38 078No figure on Docker Hub
Forks (GitHub) (differs)371 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineOn your machine (vibatchium)
Transport (differs)stdio, Streamable HTTPstdio
Tools it declares (differs)6Not published
Environment variables it asks for (differs)3, secrets among them: 2Not published
Parts of the bundle (differs)Not a bundle2
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/browserbase/mcp-server-browserbasegithub.com/trueoriginlabs/vibatchium
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 404 (16 h ago)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

In its own words, on Official MCP Registry:

MCP server for AI web browser automation using Browserbase and Stagehand

vibatchium

In its own words, on Official MCP Registry:

Stealth browser automation for AI agents — real Chrome, N parallel persistent logged-in sessions.

How to run each

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)

vibatchium As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio vibatchium -- uvx vibatchium mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.browserbase/mcp-server-browserbase has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

The marketplaces of vibatchium 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: vibatchium · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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