Ext Ops Panel
Open dashboard
Comparison

Puppeteer (Archived) vs com.mcparmory/browserbase

Puppeteer (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.mcparmory/browserbase is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplacePuppeteer (Archived)com.mcparmory/browserbase
Docker MCP Catalog Listed
Version: sha256:c1e2bda6d92d
Forks (GitHub): 11 793
Pulls (Docker Hub): 286 944
Stars (Docker Hub): 33
Stars (GitHub): 91 324
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.4
Downloads/month (PyPI): 863
Downloads/week (PyPI): 183
Forks (GitHub): 4
Stars (GitHub): 32
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

Puppeteer (Archived) vs com.mcparmory/browserbase
FactPuppeteer (Archived)com.mcparmory/browserbase
Marketplaces that list it11
Stars (GitHub) (differs)91 324 (better)32 (worse)
Pulls (Docker Hub) (differs)286 944No figure on Docker Hub
Forks (GitHub) (differs)11 793 (better)4 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/puppeteer)On your machine (mcparmory-browserbase)
Transportstdiostdio
Tools it declares (differs)7Not published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/mcparmory/registry
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

Puppeteer (Archived)

In its own words, on Docker MCP Catalog:

Browser automation and web scraping using Puppeteer.

com.mcparmory/browserbase

In its own words, on Official MCP Registry:

Create and control browser sessions for web automation, testing, and AI agent tasks

How to run each

Puppeteer (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio puppeteer -- docker run -i --rm mcp/puppeteer

com.mcparmory/browserbase As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio browserbase -- uvx mcparmory-browserbase

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

Tools each declares

The marketplaces of com.mcparmory/browserbase publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of com.mcparmory/browserbase publish no settings it asks for, so we do not compare settings.

What it can do: Puppeteer (Archived) · What it can do: com.mcparmory/browserbase · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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