Claude Code auto-memory vs Graphiti MCP Server (Zep)
Claude Code auto-memory 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.
Cost & capability
| Claude Code auto-memory | Graphiti MCP Server (Zep) | |
|---|---|---|
| Capability band | competent | competent |
| Capability composite | 70 | 50 |
| Cost tier | — | mid |
| Use cases | Code Generation Focused, Long Running Session, Offline Capable | Code Generation Focused, Long Running Session, Multi Agent Coordination, Analytical Summarization |
Where they differ (7)
Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.
| Claude Code auto-memory | Graphiti MCP Server (Zep) | |
|---|---|---|
| Capability composite | 70 | 50 |
| Use cases | Code Generation Focused, Long Running Session, Offline Capable | Code Generation Focused, Long Running Session, Multi Agent Coordination, Analytical Summarization |
| Type | Per-project file directory | Temporal KG with bi-temporal edges |
| Created | 2025-03 (Claude Code v1.0 launched Feb/Mar 2025; auto-memory feature in subsequent releases; v2.1.59+ required) | 2024-08 |
| Backend storage | file (~/.claude/projects/<project>/MEMORY.md) | Neo4j |
| Multi-tenancy | hard-isolation (per project) | namespace |
| MCP | native (first-party) — Claude Code consumes MCP | native (first-party) |
At a glance
| Claude Code auto-memory | Graphiti MCP Server (Zep) | |
|---|---|---|
| Section | Claude Code memory mechanisms | Claude Code memory mechanisms |
| Tier | T1 | T1 |
| Type | Per-project file directory | Temporal KG with bi-temporal edges |
| Created | 2025-03 (Claude Code v1.0 launched Feb/Mar 2025; auto-memory feature in subsequent releases; v2.1.59+ required) | 2024-08 |
| Latest release | — | v0.31.2 (2026-10-20) |
| License | — | Apache-2.0 |
| GitHub | — | getzep/graphiti — ~31.9k stars, last commit 2026-10 |
| Pricing | — | free tier: 2500 messages/mo + 2.5MB graph data; paid: $1.25/1000 messages + $2.50/MB extra; Enterprise custom |
| Backend storage | file (~/.claude/projects/<project>/MEMORY.md) | Neo4j |
| Deployment | — | cloud (Zep managed) or self-hosted via Graphiti OSS + Neo4j/local graph DB |
| API surface | — | MCP (stdio/HTTP) |
| Embedding | — | multiple supported |
| Multi-tenancy | hard-isolation (per project) | namespace |
| MCP | native (first-party) — Claude Code consumes MCP | native (first-party) |
| A2A | not supported | not supported |
| OpenTelemetry | searched not found | searched not found |
| Optimised for | Claude-Code-native + MCP-portable memory | Claude-Code-native + MCP-portable memory |
| Anti-fit | not for non-Claude-Code clients (some are MCP-portable) | not for non-Claude-Code clients (some are MCP-portable) |
Taxonomy
| Axis | Claude Code auto-memory | Graphiti MCP Server (Zep) |
|---|---|---|
| storage | file | graph |
| retrieval | injection | graph-traversal |
| persistence | cross-session | long-term |
| update | append-only | append-only |
| unit | fact | episode |
| governance | user-controllable | auditable |
| conflict | append | bi-temporal |
Pros & cons
Claude Code auto-memory
Pros: Per-project automatic memory built into the runtime — no plugin install, no external store, no extra prompts.
Cons: Single-vendor lock-in to Claude Code; no inspect/edit UI for what's been auto-saved; opaque to other tools.
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.