Puppeteer (Archived) vs Apify
Puppeteer (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Apify is a plugin bundle for AI coding tools published by Apify. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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
| Marketplace |   Puppeteer (Archived) |  Apify |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c1e2bda6d92d Forks (GitHub): 11 830 Pulls (Docker Hub): 289 423 Stars (Docker Hub): 33 Stars (GitHub): 91 419 Not marked · First seen |
Not listed |
| Community marketplace apify/apify-claude-code-plugin | Not listed | Listed Version: 1.0.2 Forks (GitHub): 2 Stars (GitHub): 7 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
| Fact | Puppeteer (Archived) | Apify |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 419 (better) | 7 (worse) |
| Pulls (Docker Hub) (differs) | 289 423 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 830 (better) | 2 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/puppeteer) | Remote server (mcp.apify.com) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 7 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | Not a bundle | 7 |
| Licence (differs) | NOASSERTION | Apache-2.0 |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/apify/apify-claude-code-plugin |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago, requires a key |
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)
Browser automation and web scraping using Puppeteer.
Apify
Run ready-made Actors from Apify, the largest marketplace of tools for AI, or build and publish your own.
How to run each
Puppeteer (Archived) As a local MCP server: Docker image
claude mcp add --transport stdio puppeteer -- docker run -i --rm mcp/puppeteerApify As a Claude Code plugin
/plugin marketplace add apify/apify-claude-code-plugin
/plugin install apify@apifyCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Apify has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Apify publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Apify publish no settings it asks for, so we do not compare settings.
What it can do: Puppeteer (Archived) · What it can do: Apify · 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.