Ext Ops Panel
Open dashboard
Comparison

BrowserTap MCP vs Parallel Browser MCP

BrowserTap MCP is an MCP server published by LinVireo. Marketplaces we read that list it: 1 (Official MCP Registry). Parallel Browser MCP is an MCP server published by etairl. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceBrowserTap MCPParallel Browser MCP
Official MCP Registry Listed
Version: 0.4.12
Downloads/month (PyPI): 306
Downloads/week (PyPI): 34
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.14
Downloads/month (npm): 445
Downloads/week (npm): 51
Forks (GitHub): 6
Stars (GitHub): 44
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

BrowserTap MCP vs Parallel Browser MCP
FactBrowserTap MCPParallel Browser MCP
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)44 (better)
Forks (GitHub) (differs)0 (worse)6 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (browsertap-mcp)On your machine (parallel-browser-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 08, secrets among them: 3
LicenceNot statedNot stated
Repository (differs)github.com/linvireo/browsertap-mcpgithub.com/etairl/parallel-browser-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

BrowserTap MCP

In its own words, on Official MCP Registry:

MCP server that drives the real Chrome you already use, through an extension and CDP.

Parallel Browser MCP

In its own words, on Official MCP Registry:

MCP server for parallel browser automation across multiple providers.

How to run each

BrowserTap MCP As a local MCP server: PyPI package

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

Parallel Browser MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "ANCHOR_API_KEY=<YOUR_ANCHOR_API_KEY>" --env "BROWSERBASE_API_KEY=<YOUR_BROWSERBASE_API_KEY>" --env "CLOUDFLARE_API_TOKEN=<YOUR_CLOUDFLARE_API_TOKEN>" --transport stdio parallel-browser-mcp -- npx -y parallel-browser-mcp

Requires: ANCHOR_API_KEY (secret), BROWSERBASE_API_KEY (secret), CLOUDFLARE_API_TOKEN (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only BrowserTap MCP asks for

  • BROWSERTAP_BRIDGE_PORT
  • BROWSERTAP_MODE
  • BROWSERTAP_PREFERRED_BROWSER
  • BROWSERTAP_STATE_DIR

Only Parallel Browser MCP asks for

  • ANCHOR_API_KEY (secret)
  • BROWSERBASE_API_KEY (secret)
  • BROWSERBASE_PROJECT_ID
  • BROWSER_MCP_CONFIG
  • BROWSER_MCP_CONFIG_PATH
  • CLOUDFLARE_ACCOUNT_ID
  • CLOUDFLARE_API_TOKEN (secret)
  • PLAYWRIGHT_USE_CLOAKBROWSER

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

What it can do: BrowserTap MCP · What it can do: Parallel Browser MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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