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 | MCPVault for ObsidianMCP100 Recommended | Codebase Memory MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation BitBonsai · Publisher source ↗ | First-party MCP DeusData · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Sep 21, 2026 Package: Not documented | Repo: Aug 14, 2026 Package: Aug 14, 2026 |
| Popularity evidence | ||
| GitHub stars | 1,672 GitHub stars · checked 2026-09-24T04:14:39.538000Z | 44,904 GitHub stars · checked 2026-09-25T18:35:00Z |
| Package downloads / 30 days | No reliable download data | 28,000 package downloads / 30 days · checked 2026-08-14T00:00:00.000Z |
| External adoption evidence | Not documented |
|
| 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 | None at the local stdio layer. | local stdio; no remote auth needed |
| Cost | MCPVault is MIT licensed and free to run locally. MCP-host, model, backup, and storage costs remain. | none beyond local resources |
| Permissions | 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. | reads indexed source/project data; installer writes supported agent/editor configs/hooks |
| Data handling | 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. | local processing; current docs state no source/index/query/env/telemetry upload |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | 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. | latest 0.10.x supported; SLSA/Sigstore/checksums/VirusTotal/security policy |
| Evidence date | ||
| Editorial review | 2026-09-05 | 2026-09-23 |
| Candidate evidence | 2026-09-24T04:25:05.554391Z | 2026-09-25T18:35:00Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →