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.
| Evidence field | Docling MCPWatchlist candidate | Excel MCP ServerMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Docling Project · Publisher source ↗ | Community implementation Haris Musa · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 14, 2026 Package: Aug 14, 2026 | Repo: Apr 12, 2026 Package: Apr 12, 2026 |
| Popularity evidence | ||
| GitHub stars | 707 GitHub stars · checked 2026-08-14T18:46:26.000Z | 4,108 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | 38,665 PyPI Stats package downloads · checked 2026-08-14T18:46:26.000Z | No reliable download data |
| External adoption evidence |
|
|
| 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 note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Local 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. | Local stdio has no separate service authentication. Remote MCP authentication is not documented, so remote listeners must remain network-restricted. |
| Cost | The 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. | The MIT-licensed local server lists no usage fee; normal hosting, client, model, and network costs may apply. |
| Permissions | The 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 can read, create, modify, format, chart, and delete workbook content. Remote modes confine relative paths to EXCEL_FILES_PATH in the patched release. |
| Data handling | Local 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 Watchlist gap. | Workbook paths and spreadsheet content are processed by the server and returned to the connected client as required by tool calls; publisher telemetry and retention are not documented. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Choose 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. | Versions through 0.1.7 have a critical path-traversal vulnerability. Use 0.1.8 or later, prefer stdio, restrict workbook paths, avoid public remote listeners, and keep recoverable backups. |
| Evidence date | ||
| Editorial review | 2026-08-14 | 2026-08-13 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →