Ext Ops Panel
Open dashboard
Comparison

Puppeteer (Archived) vs Orchestrate

Puppeteer (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Orchestrate is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). As of our marketplace pass on 2026-10-12. 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)Orchestrate
Docker MCP Catalog Listed
Version: sha256:c1e2bda6d92d
Forks (GitHub): 11 778
Pulls (Docker Hub): 281 970
Stars (Docker Hub): 33
Stars (GitHub): 91 146
Not marked · First seen
Not listed
Cursor: cursor/plugins Not listed Listed
Version: 1.1.0
No figure published
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 Orchestrate
FactPuppeteer (Archived)Orchestrate
Marketplaces that list it11
Stars (GitHub) (differs)91 146No figure on GitHub
Pulls (Docker Hub) (differs)281 970No figure on Docker Hub
Forks (GitHub) (differs)11 778No figure on GitHub
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
Parts of the bundle (differs)Not a bundle1
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/cursor/plugins
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.

Orchestrate

In its own words, on Cursor: cursor/plugins:

Fan large tasks out across parallel cloud agents with planners, workers, verifiers, and structured handoffs.

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

Orchestrate

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

Settings each asks for

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

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

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. 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