Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldDocling MCPShortlist candidateMCPVault for ObsidianMCP100 Recommended
Task fit
Best for
  • Parsing PDF, DOCX, XLSX, PPTX, CSV, and HTML into structured DoclingDocument, Markdown, or JSON output
  • PDF table structure, OCR-enabled conversion, and derived structured-document workflows
  • Obsidian users who want local search and supervised note maintenance
  • Vaults protected by version control or reliable backups
  • Users able to expose only a dedicated, bounded vault
Not ideal for
  • Editing the original PDF, DOCX, XLSX, PPTX, or CSV source file
  • Clients that cannot use the current MCP SDK v2-compatible Docling MCP 3.x release
  • Unbacked-up personal knowledge bases
  • Read-only research where a simpler filesystem search is sufficient
  • Enterprise knowledge requiring centralized authorization and audit controls
Avoid when
  • Remote conversion would send sensitive documents to an endpoint whose retention and access controls you have not approved
  • You cannot constrain or review update and delete operations on cached DoclingDocument content
  • The vault contains secrets, regulated data, or material that cannot reach the selected AI provider
  • Write, move, and delete tools cannot be confirmed by a human
  • The vault path cannot be narrowed to a dedicated directory
Provenance
Provenance details

First-party MCP

Docling Project · Publisher source ↗

Community implementation

BitBonsai · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 14, 2026

Package: Aug 14, 2026

Repo: Sep 21, 2026

Package: Not documented

Popularity evidence
GitHub stars

707

GitHub stars · checked 2026-08-14T18:46:26.000Z

1,672

GitHub stars · checked 2026-09-24T04:14:39.538000Z

Package downloads / 30 days

38,665

package downloads / 30 days · checked 2026-08-14T18:46:26.000Z

No reliable download data
Client coverage
Client coverage details
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationLocal stdio mode does not require a service credential. Remote mode uses the configured Docling Serve URL and optional API key; additional integrations may require separate keys.None at the local stdio layer.
CostThe MIT-licensed local software has no documented MCP fee. Hosting Docling Serve, storage, model endpoints, or optional managed services may incur infrastructure or provider charges.MCPVault is MIT licensed and free to run locally. MCP-host, model, backup, and storage costs remain.
PermissionsThe server can read local paths and URLs, access configured object-storage sources, cache documents, and expose tools that update or delete items in derived DoclingDocument state.The server has filesystem read and write access within the supplied vault root, including note creation, overwrite or patch, frontmatter changes, moves, tags, and deletion. Operating-system permissions and the configured vault path are the primary boundary.
Data handlingLocal mode processes and caches documents on the host. Remote mode sends document content to the configured Docling Serve URL; storage-provider and RAG extras add their own data paths. The current privacy document still says processing is local, so that conflict remains an explicit Shortlist gap.Vault content and metadata are read locally and returned to the MCP client and model. Changes are written directly to local files. MCPVault states that it does not receive, store, or transmit vault data, while the selected AI provider still processes content sent by the client.
Limitations
Tradeoffs
  • Local mode keeps conversion on the host but installs the larger Docling stack; remote mode is lighter but sends documents to Docling Serve.
  • A rich conversion and generation surface improves task fit while increasing the permissions and failure modes that need review.
  • Local stdio avoids a hosted MCP service, but note contents still enter the MCP host and model context.
  • Frontmatter-aware writes are more useful than generic file access but increase integrity risk.
  • npx makes setup simple, while stricter environments may prefer a pinned and reviewed package version.
  • Version 0.16.0 migrated to MCP TypeScript SDK v2 / protocol 2026-07-28 while retaining dual-era stdio compatibility.
Risk contextChoose local versus remote mode explicitly, restrict readable paths and source URLs, approve the remote retention boundary, disable unused conversion, generation, or manipulation tools, and pin a client-compatible release. Update and delete operations affect cached derived DoclingDocument state rather than the original source file, but remain destructive within that state.A selected vault can contain a large body of private knowledge, and write tools can overwrite, move, or delete it. Use a dedicated vault, reliable backups or version control, an absolute path, a reviewed package version, and explicit approval for writes.
Evidence date
Editorial review2026-08-142026-09-05
Candidate evidence2026-08-14T18:46:26.000Z2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →