Ext Ops Panel
Open dashboard
Comparison

Puppeteer (Archived) vs chromeflow

Puppeteer (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). chromeflow is a plugin bundle for AI coding tools published by neodrew. Marketplaces we read that list it: 1 (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
MarketplacePuppeteer (Archived)chromeflow
Docker MCP Catalog Listed
Version: sha256:c1e2bda6d92d
Forks (GitHub): 11 790
Pulls (Docker Hub): 284 530
Stars (Docker Hub): 33
Stars (GitHub): 91 268
Not marked · First seen
Not listed
Community marketplace neodrew/chromeflow Not listed Listed
Version: 0.13.18
Forks (GitHub): 0
Stars (GitHub): 3
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 chromeflow
FactPuppeteer (Archived)chromeflow
Marketplaces that list it11
Stars (GitHub) (differs)91 268 (better)3 (worse)
Pulls (Docker Hub) (differs)284 530No figure on Docker Hub
Forks (GitHub) (differs)11 790 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/puppeteer)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)7Not published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Hooks it runs (differs)Not published4
Parts of the bundle (differs)Not a bundle3
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/neodrew/chromeflow
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

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.

chromeflow

In its own words, on Community GitHub marketplaces:

Let Claude Code drive your real browser — clicks, fills forms, grabs API keys, writes them to .env.

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

chromeflow As a Claude Code plugin

Claude Code
/plugin marketplace add neodrew/chromeflow
/plugin install chromeflow@chromeflow

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

Tools each declares

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

Settings each asks for

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

What it can do: Puppeteer (Archived) · What it can do: chromeflow · Compare two other plugins

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