Ext Ops Panel
Open dashboard
Comparison

Puppeteer (Archived) vs Oya Browser

Puppeteer (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Oya Browser is an MCP server published by OyadotAI. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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)Oya Browser
Docker MCP Catalog Listed
Version: sha256:c1e2bda6d92d
Forks (GitHub): 11 807
Pulls (Docker Hub): 287 249
Stars (Docker Hub): 33
Stars (GitHub): 91 346
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.198
Forks (GitHub): 278
Stars (GitHub): 352
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 Oya Browser
FactPuppeteer (Archived)Oya Browser
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)91 346 (better)352 (worse)
Pulls (Docker Hub) (differs)287 249No figure on Docker Hub
Forks (GitHub) (differs)11 807 (better)278 (worse)
Last release (differs)Not published2026-10-18
Where it runs (differs)On your machine (mcp/puppeteer)Remote server (oyabrowser.com/mcp/pool)
Transport (differs)stdioStreamable HTTP
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 bundle2
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/oyadotai/oya-browser
Changes in the last 7 days (differs)020 or more
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 25 h 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)

In its own words, on Docker MCP Catalog:

Browser automation and web scraping using Puppeteer.

Oya Browser

In its own words, on Official MCP Registry:

Real Chrome for agents: start a browser, read pages as numbered markdown, click, type, hand off.

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

Oya Browser As a remote MCP server

Claude Code
claude mcp add --transport http oya-browser https://oyabrowser.com/mcp/pool --header "Authorization: Bearer <YOUR_API_KEY>"

Requires: Authorization header

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

Only Oya Browser has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

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

What it can do: Puppeteer (Archived) · What it can do: Oya Browser · 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. 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