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

Graphiti MCPMCPVault for Obsidian

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

Comparable alternatives

AWS Documentation MCPMCP100 SelectedAsana MCPMCP100 SelectedAtlassian Remote MCPMCP100 SelectedAzure MCP ServerMCP100 SelectedCanva Dev MCPMCP100 SelectedChrome DevTools MCPMCP100 Selected

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Graphiti MCPWatchlist candidate	MCPVault for ObsidianMCP100 Selected
Task fit
Best for	Self-hosted persistent memory and knowledge-graph workflows Teams willing to isolate the service behind network/auth controls	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	Internet-exposed deployments without a reverse proxy or other access control Production memory stores that require built-in strong authentication	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	You would expose the default 0.0.0.0 HTTP endpoint on an untrusted network You cannot back up or recover graph data before enabling delete/clear tools	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 Zep / getzep · Publisher source ↗	Community implementation BitBonsai · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Aug 13, 2026 Package: Aug 9, 2026
Popularity evidence
GitHub stars	Not documented	1,613 GitHub stars · checked 2026-08-14T18:46:26.000Z
Package downloads / 30 days	No reliable download data	50,394 package downloads / 30 days · checked 2026-09-08
External adoption evidence	Not documented	npm: package downloads: 64,139Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details	Not documented	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	Current MCP server docs do not establish built-in HTTP authentication as a default control; deployments should rely on local access or external network/reverse-proxy controls.	None at the local stdio layer.
Cost	Open-source server; database and LLM/embedder provider costs apply.	MCPVault is MIT licensed and free to run locally. MCP-host, model, backup, and storage costs remain.
Permissions	Tools include add/search plus delete_episode, delete_entity_edge, and clear_graph. Database privileges are those of the configured Neo4j/FalkorDB credentials.	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	Stores knowledge-graph episodes/entities/facts and uses configured LLM/embedder providers during ingestion/search. Anonymous telemetry can be disabled.	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	Rich memory tools are valuable but include destructive operations Multiple LLM/database credentials increase the deployment's secret surface	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 context	High. Default network exposure plus destructive graph tools and backend/LLM credentials create material unauthorized-access and data-loss risk.	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-09-11	2026-09-05
Candidate evidence	2026-09-11T00:00:00.000Z	2026-09-05T00:00:00.000Z

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

Read the evidence method →