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 | MCPVault for ObsidianMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| 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: Aug 13, 2026 Package: Aug 9, 2026 |
| Popularity evidence | ||
| GitHub stars | 707 GitHub stars · checked 2026-08-14T18:46:26.000Z | 1,613 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 | 64,139 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. | None at the local stdio layer. |
| 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. | MCPVault is MIT licensed and free to run locally. MCP-host, model, backup, and storage costs remain. |
| 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 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 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. | 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 |
|
|
| 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. | 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 review | 2026-08-14 | 2026-07-24 |
| 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 →