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

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

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldGraphiti MCPShortlist candidateMCPVault for ObsidianMCP100 Recommended
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

reviewed-detail:graphiti-mcp · Publisher source ↗

Community implementation

BitBonsai · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Sep 21, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

1,672

GitHub stars · checked 2026-09-24T04:14:39.538000Z

Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationCurrent 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.
CostOpen-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.
PermissionsTools 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 handlingStores 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 contextHigh. 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 review2026-09-112026-09-05
Candidate evidence2026-09-11T00:00:00.000Z2026-09-24T04:25:05.554391Z

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

Read the evidence method →