Puppeteer (Archived) vs PySide6 MCP
Puppeteer (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). PySide6 MCP is an MCP server published by com55. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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) |  PySide6 MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c1e2bda6d92d Forks (GitHub): 11 830 Pulls (Docker Hub): 288 670 Stars (Docker Hub): 33 Stars (GitHub): 91 419 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Downloads/month (PyPI): 159 Downloads/week (PyPI): 35 Forks (GitHub): 2 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
| Fact | Puppeteer (Archived) | PySide6 MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 91 419 (better) | 6 (worse) |
| Pulls (Docker Hub) (differs) | 288 670 | 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) | On your machine (pyside6-mcp) |
| Transport | stdio | stdio |
| 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 | 2 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/com55/pyside6-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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)
Browser automation and web scraping using Puppeteer.
PySide6 MCP
Playwright-style MCP to inspect, control, and debug PySide6 desktop GUIs.
How to run each
Puppeteer (Archived) As a local MCP server: Docker image
claude mcp add --transport stdio puppeteer -- docker run -i --rm mcp/puppeteerPySide6 MCP As a local MCP server: PyPI package
claude mcp add --transport stdio pyside6-mcp -- uvx pyside6-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of PySide6 MCP publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of PySide6 MCP publish no settings it asks for, so we do not compare settings.
What it can do: Puppeteer (Archived) · What it can do: PySide6 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. 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.