Ext Ops Panel
Open dashboard
Comparison

One MCP, many parsers vs PapersFlow

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). PapersFlow is an MCP server published by papersflow-ai. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
MarketplaceOne MCP, many parsersPapersFlow
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 14
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

One MCP, many parsers vs PapersFlow
FactOne MCP, many parsersPapersFlow
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)0 (worse)14 (better)
Forks (GitHub)11
Last releaseNot publishedNot published
Where it runs (differs)On your machine (https://github.com/adelaidasofia/parse-mcp/releases/download/v0.1.0/parse-mcp.mcpb)Remote server (doxa.papersflow.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/adelaidasofia/parse-mcpgithub.com/papersflow-ai/papersflow-mcp
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

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

In its own words, on Official MCP Registry:

One MCP, many parsers. Routes between markitdown, Docling, and LlamaParse. Plus an interpret tool…

PapersFlow

In its own words, on Official MCP Registry:

Academic research MCP server for paper search, citation checks, graphs, and deep research.

How to run each

One MCP, many parsers As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install parse-mcp@claude-community

Requires: LLAMAPARSE_API_KEY (secret)

PapersFlow As a remote MCP server

Claude Code
claude mcp add --transport http papersflow https://doxa.papersflow.ai/mcp

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

Only PapersFlow has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: One MCP, many parsers · What it can do: PapersFlow · 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.

Where the data comes from: how the catalog is built