io.github.ParserBee/parserbee-mcp vs io.github.groupdocs-parser/groupdocs-parser-mcp
io.github.ParserBee/parserbee-mcp is an MCP server published by ParserBee. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.groupdocs-parser/groupdocs-parser-mcp is an MCP server published by groupdocs-parser. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 26.10.2 Forks (GitHub): 0 Stars (GitHub): 0 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 | io.github.ParserBee/parserbee-mcp | io.github.groupdocs-parser/groupdocs-parser-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (parserbee-mcp) | On your machine (ghcr.io/groupdocs-parser/parser-net-mcp:26.10.2) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 5, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/parserbee/parserbee-mcp | github.com/groupdocs-parser/groupdocs.parser.mcp |
| Changes in the last 7 days (differs) | 2 | 3 |
| First seen (differs) | 2026-10-14 | 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
io.github.ParserBee/parserbee-mcp
Extract structured data from invoices, receipts and other documents with ParserBee.
io.github.groupdocs-parser/groupdocs-parser-mcp
MCP server for GroupDocs.Parser — extract text, images, metadata, tables, barcodes via AI.
How to run each
io.github.ParserBee/parserbee-mcp As a local MCP server: npm package
claude mcp add --env "PARSERBEE_API_KEY=<YOUR_PARSERBEE_API_KEY>" --transport stdio parserbee-mcp -- npx -y parserbee-mcp
Requires: PARSERBEE_API_KEY (secret)
io.github.groupdocs-parser/groupdocs-parser-mcp As a local MCP server: Docker image
claude mcp add --transport stdio groupdocs-parser-mcp -- docker run -i --rm ghcr.io/groupdocs-parser/parser-net-mcp:26.10.2
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 io.github.ParserBee/parserbee-mcp asks for
PARSERBEE_API_KEY (secret)
Only io.github.groupdocs-parser/groupdocs-parser-mcp asks for
GROUPDOCS_LICENSE_PATHGROUPDOCS_MCP_OUTPUT_PATHGROUPDOCS_MCP_STORAGE_PATHGROUPDOCS_METERED_PRIVATE_KEYGROUPDOCS_METERED_PUBLIC_KEY
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.ParserBee/parserbee-mcp · What it can do: io.github.groupdocs-parser/groupdocs-parser-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.