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 | Codebase MemoryMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Docling Project · Publisher source ↗ | Community implementation io.github.DeusData · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 14, 2026 Package: Aug 14, 2026 | Repo: Aug 14, 2026 Package: Aug 14, 2026 |
| Popularity evidence | ||
| GitHub stars | 707 GitHub stars · checked 2026-08-14T18:46:26.000Z | 38,935 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 | 28,015 30-day package downloads · checked 2026-08-14T18:46:26.000Z |
| 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. | No authentication or API key is documented for local stdio. CBM_ALLOWED_ROOT is an optional filesystem containment control; no containment is imposed when it is unset. |
| 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 native software lists no service fee. Local storage and package-manager costs are separate. |
| 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. | Indexes repositories, queries code and graphs, performs architecture and impact analysis, manages ADRs and watchers, deletes projects, and writes agent configuration, instruction, Skill, and hook files. |
| 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. | The publisher says processing is local and code does not leave the machine. Indexes, embeddings, memories, SQLite data, and logs persist under the local CBM cache directory. |
| 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. | Indexing can capture sensitive files, while persistent graph data and installer/configuration writes expand local exposure. Set CBM_ALLOWED_ROOT, protect the cache, and use explicit project paths. |
| Evidence date | ||
| Editorial review | 2026-08-14 | 2026-08-11 |
| 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 →