Ext Ops Panel
Open dashboard
Comparison

Docling MCP vs PDF to Markdown & Document Parser

Docling MCP is an MCP server published by docling-project. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). PDF to Markdown & Document Parser is an MCP server published by fernandoguiraud16-coder. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceDocling MCPPDF to Markdown & Document Parser
Official MCP Registry Listed
Version: 3.3.0
Downloads/month (PyPI): 20 338
Downloads/week (PyPI): 4 734
Forks (GitHub): 144
Stars (GitHub): 777
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
PyPI (MCP servers) Listed
Version: 3.3.0
Downloads/month (PyPI): 20 338
Downloads/week (PyPI): 4 734
Forks (GitHub): 144
Stars (GitHub): 777
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

Docling MCP vs PDF to Markdown & Document Parser
FactDocling MCPPDF to Markdown & Document Parser
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)777 (better)0 (worse)
Forks (GitHub) (differs)144 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (docling-mcp)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)14, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/docling-project/docling-mcpgithub.com/fernandoguiraud16-coder/data-tools
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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

Docling MCP

In its own words, on Official MCP Registry:

Convert PDFs and other documents to structured formats via Docling, for AI applications.

PDF to Markdown & Document Parser

In its own words, on Official MCP Registry:

Convert PDF, Word, Excel and scanned documents to Markdown, tables and RAG chunks. OCR.

How to run each

Docling MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "DOCLING_MCP_SERVICE_API_KEY=<YOUR_DOCLING_MCP_SERVICE_API_KEY>" --transport stdio docling-mcp -- uvx --from docling-mcp==3.3.0 docling-mcp-server --transport stdio docling-mcp

Requires: DOCLING_MCP_SERVICE_API_KEY (secret)

PDF to Markdown & Document Parser

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Only PDF to Markdown & Document Parser 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 PDF to Markdown & Document Parser publish no settings it asks for, so we do not compare settings.

What it can do: Docling MCP · What it can do: PDF to Markdown & Document Parser · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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