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 MCPCodebase Memory

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	Codebase MemoryMCP100 Selected
Task fit
Best for	Self-hosted persistent memory and knowledge-graph workflows Teams willing to isolate the service behind network/auth controls	Repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages
Not ideal for	Internet-exposed deployments without a reverse proxy or other access control Production memory stores that require built-in strong authentication	Tiny repositories, one-off text searches, or semantic questions unsupported by the indexed parsers
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 source tree cannot be indexed locally or persistent cache files are prohibited
Provenance
Provenance details	First-party MCP Zep / getzep · Publisher source ↗	Community implementation io.github.DeusData · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Aug 14, 2026 Package: Aug 14, 2026
Popularity evidence
GitHub stars	Not documented	38,935 GitHub stars · checked 2026-08-14T18:46:26.000Z
Package downloads / 30 days	No reliable download data	28,015 package downloads / 30 days · checked 2026-09-08
External adoption evidence	Not documented	npm: package downloads: 28,015Exact 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.	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	Open-source server; database and LLM/embedder provider costs apply.	The MIT-licensed native software lists no service fee. Local storage and package-manager costs are separate.
Permissions	Tools include add/search plus delete_episode, delete_entity_edge, and clear_graph. Database privileges are those of the configured Neo4j/FalkorDB credentials.	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	Stores knowledge-graph episodes/entities/facts and uses configured LLM/embedder providers during ingestion/search. Anonymous telemetry can be disabled.	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	Rich memory tools are valuable but include destructive operations Multiple LLM/database credentials increase the deployment's secret surface	Persistent indexing can reduce repeated reads, but consumes local storage and graph results can become stale until the repository is re-indexed. Version 0.10.8 includes correctness and reliability fixes affecting graph/search results and Windows behavior.
Risk context	High. Default network exposure plus destructive graph tools and backend/LLM credentials create material unauthorized-access and data-loss risk.	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-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 →