Fetch (Reference) vs Documents to Data (PDF to Markdown, document to JSON)
Fetch (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). Documents to Data (PDF to Markdown, document to JSON) is an MCP server published by owlabee. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:1a7a0996a565 Forks (GitHub): 11 941 Pulls (Docker Hub): 1 988 111 Stars (Docker Hub): 59 Stars (GitHub): 91 934 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Listed Version: 2026.11.11 Downloads/month (PyPI): 506 506 Downloads/week (PyPI): 288 522 Forks (GitHub): 11 941 Stars (GitHub): 91 934 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.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 | Fetch (Reference) | Documents to Data (PDF to Markdown, document to JSON) |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 91 934 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 1 988 111 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 941 (better) | 0 (worse) |
| Last release (differs) | 2026-11-11 (better) | 2026-11-07 (worse) |
| Where it runs (differs) | On your machine (mcp/fetch) | Remote server (mcp.apify.com) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/owlabee/owlabee |
| Changes in the last 7 days (differs) | 1 | 3 |
| First seen (differs) | 2026-10-11 | 2026-11-07 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 1 h ago, requires authentication |
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
Fetch (Reference)
Fetches a URL from the internet and extracts its contents as markdown.
Documents to Data (PDF to Markdown, document to JSON)
Turn PDFs, documents, podcasts and drone photos into Markdown, structured JSON, summaries, reports.
How to run each
Fetch (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio fetch -- docker run -i --rm mcp/fetch
Documents to Data (PDF to Markdown, document to JSON)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Documents to Data (PDF to Markdown, document to JSON) has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Documents to Data (PDF to Markdown, document to JSON) publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Fetch (Reference) · What it can do: Documents to Data (PDF to Markdown, document to JSON) · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). 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.