Ext Ops Panel
Open dashboard
Comparison

Puppeteer (Archived) vs chrome-mcp

chrome-mcp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.

Puppeteer (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). chrome-mcp is an MCP server published by Mehmoodqureshi. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacePuppeteer (Archived)chrome-mcp
Docker MCP Catalog Listed
Version: sha256:c1e2bda6d92d
Forks (GitHub): 11 871
Pulls (Docker Hub): 294 784
Stars (Docker Hub): 33
Stars (GitHub): 91 595
Not marked · First seen
Not listed
Official MCP Registry Not listed Removed on 2026-10-16
Version: 0.9.25
Downloads/month (npm): 4 390
Downloads/week (npm): 1 498
Forks (GitHub): 0
Stars (GitHub): 6
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 chrome-mcp
FactPuppeteer (Archived)chrome-mcpno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)91 5956
Pulls (Docker Hub) (differs)294 784No figure on Docker Hub
Forks (GitHub) (differs)11 8710
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/puppeteer)On your machine (@mehmoodqureshi/chrome-mcp)
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/mehmoodqureshi/chrome-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. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of chrome-mcp

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • MCP Browser Extension

    Drive your real Chrome over MCP: real logins and cookies, multi-tab automation, deny-all by default.

    by Mehmoodqureshi · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • agent-webbridge io.github.jeet-dhandha/agent-webbridge

    Drive your real, logged-in Chrome (many profiles, parallel tabs) from any MCP client. Local only.

    by jeet-dhandha · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • browser io.github.cherchyk/browser

    MCP server for loading authenticated web pages using Chrome DevTools Protocol

    by cherchyk · MCP server

    Listed on: Official MCP Registry, npm registry (MCP servers) · Describes nearly the same job

  • browser-mcp io.github.Shreyas-Profile/browser-mcp

    Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.

    by Shreyas-Profile · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • weboperator io.github.KazKozDev/weboperator

    Hands your live Chrome tab to any MCP client — snapshot, navigate, click, type, extract.

    by KazKozDev · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • real-browser io.github.ofershap/real-browser

    MCP server + Chrome extension for AI browser control with real sessions.

    by ofershap · MCP server

    Listed on: Official MCP Registry, npm registry (MCP servers) · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

Puppeteer (Archived)

In its own words, on Docker MCP Catalog:

Browser automation and web scraping using Puppeteer.

chrome-mcp

In its own words, on Official MCP Registry:

Drive your real Chrome over MCP: real logins and cookies, multi-tab automation, deny-all by default.

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

chrome-mcp

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 chrome-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of chrome-mcp publish no settings it asks for, so we do not compare settings.

What it can do: Puppeteer (Archived) · What it can do: chrome-mcp · 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