codebase-memory-mcp (DeusData) vs Graphiti MCP Server (Zep)

codebase-memory-mcp (DeusData) vs Graphiti MCP Server (Zep): side-by-side comparison of two claude code memory mechanisms systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.

codebase-memory-mcp (DeusData) · Graphiti MCP Server (Zep)

Compare any two systems →

Cost & capability

codebase-memory-mcp (DeusData)Graphiti MCP Server (Zep)
Capability bandcompetentcompetent
Capability composite4550
Cost tierfreemid
$/Mtok input0—
$/Mtok output0—
Use casesCode Generation Focused, Long Running Session, Offline Capable, Analytical SummarizationCode Generation Focused, Long Running Session, Multi Agent Coordination, Analytical Summarization

Where they differ (15)

Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.

codebase-memory-mcp (DeusData)Graphiti MCP Server (Zep)
Capability composite4550
Cost tierfreemid
Use casesCode Generation Focused, Long Running Session, Offline Capable, Analytical SummarizationCode Generation Focused, Long Running Session, Multi Agent Coordination, Analytical Summarization
TypeTree-sitter knowledge-graph MCP for codeTemporal KG with bi-temporal edges
Created2026 (active 2026 release cadence; latest v0.6.1 2026-05-04)2024-08
Latest releasev0.11.0 (2026-09-15)v0.31.2 (2026-10-20)
LicenseMITApache-2.0
GitHubDeusData/codebase-memory-mcp — ~43.3k stars, last release 2026-09getzep/graphiti — ~31.9k stars, last commit 2026-10
Pricingfree / open source (MIT); no paid tierfree tier: 2500 messages/mo + 2.5MB graph data; paid: $1.25/1000 messages + $2.50/MB extra; Enterprise custom
Backend storageSQLite (WAL mode) at ~/.cache/codebase-memory-mcp/Neo4j
DeploymentLocal — single static binary (macOS arm64/amd64; Linux arm64/amd64; Windows amd64)cloud (Zep managed) or self-hosted via Graphiti OSS + Neo4j/local graph DB
API surfaceMCP (stdio) — 14 tools incl. index_repository / search_graph / trace_call_path / query_graph (Cypher-like) / get_architecture / detect_changes / manage_adr / search_code / get_code_snippet / ingest_traces / list_projects / delete_project / index_status / get_graph_schemaMCP (stdio/HTTP)
MCPnative (first-party MCP server)native (first-party)
Optimised forstructural code knowledge graphs (token-efficient; 99.2% reduction vs grep) + sub-ms queries + 155-language tree-sitter coverageClaude-Code-native + MCP-portable memory
Anti-fitnot for non-code memory; not for natural-language conversation memory; SEMANTICALLY_RELATED edges require optional embedding pipelinenot for non-Claude-Code clients (some are MCP-portable)

At a glance

codebase-memory-mcp (DeusData)Graphiti MCP Server (Zep)
SectionClaude Code memory mechanisms Claude Code memory mechanisms
TierT1 T1
TypeTree-sitter knowledge-graph MCP for code Temporal KG with bi-temporal edges
Created2026 (active 2026 release cadence; latest v0.6.1 2026-05-04) 2024-08
Latest releasev0.11.0 (2026-09-15) v0.31.2 (2026-10-20)
LicenseMIT Apache-2.0
GitHubDeusData/codebase-memory-mcp — ~43.3k stars, last release 2026-09 getzep/graphiti — ~31.9k stars, last commit 2026-10
Pricingfree / open source (MIT); no paid tier free tier: 2500 messages/mo + 2.5MB graph data; paid: $1.25/1000 messages + $2.50/MB extra; Enterprise custom
Fundingsearched not found —
Backend storageSQLite (WAL mode) at ~/.cache/codebase-memory-mcp/ Neo4j
DeploymentLocal — single static binary (macOS arm64/amd64; Linux arm64/amd64; Windows amd64) cloud (Zep managed) or self-hosted via Graphiti OSS + Neo4j/local graph DB
API surfaceMCP (stdio) — 14 tools incl. index_repository / search_graph / trace_call_path / query_graph (Cypher-like) / get_architecture / detect_changes / manage_adr / search_code / get_code_snippet / ingest_traces / list_projects / delete_project / index_status / get_graph_schema MCP (stdio/HTTP)
Embedding— multiple supported
Multi-tenancy— namespace
MCPnative (first-party MCP server) native (first-party)
A2Anot supported not supported
OpenTelemetrysearched not found searched not found
Optimised forstructural code knowledge graphs (token-efficient; 99.2% reduction vs grep) + sub-ms queries + 155-language tree-sitter coverage Claude-Code-native + MCP-portable memory
Anti-fitnot for non-code memory; not for natural-language conversation memory; SEMANTICALLY_RELATED edges require optional embedding pipeline not for non-Claude-Code clients (some are MCP-portable)

Taxonomy

Axiscodebase-memory-mcp (DeusData)Graphiti MCP Server (Zep)
storagegraphgraph
retrievalstructural-querygraph-traversal
persistenceproject-boundlong-term
updatereplacementappend-only
unitfactepisode
governanceuser-controllableauditable
conflictdeterministic-overwritebi-temporal

Pros & cons

codebase-memory-mcp (DeusData)

Pros: Single-binary zero-deps deployment; 155-language tree-sitter coverage; structural queries replace grep at 120x fewer tokens; SLSA-3 + Sigstore + VirusTotal; team-shared graph artifact format; preprint with reproduction-friendly evaluation.

Cons: Preprint not peer-reviewed; founders/company opaque (DeusData has no disclosed principals); no managed/cloud option; SEMANTICALLY_RELATED edges depend on optional embedding pipeline.

Graphiti MCP Server (Zep)

Pros: MCP exposure of Graphiti's bi-temporal KG gives any agent contradiction-aware memory; first-party vendor support.

Cons: KG memory is heavier than vector for the same data; MCP setup more involved than installing an embedded SDK.

Rows last verified 2026-10-22 / 2026-10-22. Data is CC-BY-4.0 — see how to read this.