One MCP, many parsers vs Suparse Document Processing
One MCP, many parsers is an MCP server published by adelaidasofia. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). Suparse Document Processing is an MCP server published by suparse. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  One MCP, many parsers |  Suparse Document Processing |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.5.0 Downloads/month (npm): 768 Downloads/week (npm): 97 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Not listed |
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 | One MCP, many parsers | Suparse Document Processing |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | On your machine (https://github.com/adelaidasofia/parse-mcp/releases/download/v0.1.0/parse-mcp.mcpb) | On your machine (@suparse/mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/adelaidasofia/parse-mcp | github.com/suparse/suparse-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| 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
One MCP, many parsers
One MCP, many parsers. Routes between markitdown, Docling, and LlamaParse. Plus an interpret tool…
Suparse Document Processing
Extract data, create schemas, and export results from PDFs and documents with Suparse AI OCR.
How to run each
One MCP, many parsers As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install parse-mcp@claude-communityRequires: LLAMAPARSE_API_KEY (secret)
Suparse Document Processing As a local MCP server: npm package
claude mcp add --env "SUPARSE_API_KEY=<YOUR_SUPARSE_API_KEY>" --transport stdio suparse-mcp -- npx -y @suparse/mcpRequires: SUPARSE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only One MCP, many parsers asks for
LLAMAPARSE_API_KEY (secret)
Only Suparse Document Processing asks for
SUPARSE_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: One MCP, many parsers · What it can do: Suparse Document Processing · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.