Claude Code auto-memory vs codebase-memory-mcp (DeusData)
Claude Code auto-memory vs codebase-memory-mcp (DeusData): side-by-side comparison of two claude code memory mechanisms systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.
Claude Code auto-memory · codebase-memory-mcp (DeusData)
Cost & capability
| Claude Code auto-memory | codebase-memory-mcp (DeusData) | |
|---|---|---|
| Capability band | competent | competent |
| Capability composite | 70 | 45 |
| Cost tier | — | free |
| $/Mtok input | — | 0 |
| $/Mtok output | — | 0 |
| Use cases | Code Generation Focused, Long Running Session, Offline Capable | Code Generation Focused, Long Running Session, Offline Capable, Analytical Summarization |
Where they differ (8)
Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.
| Claude Code auto-memory | codebase-memory-mcp (DeusData) | |
|---|---|---|
| Capability composite | 70 | 45 |
| Use cases | Code Generation Focused, Long Running Session, Offline Capable | Code Generation Focused, Long Running Session, Offline Capable, Analytical Summarization |
| Type | Per-project file directory | Tree-sitter knowledge-graph MCP for code |
| Created | 2025-03 (Claude Code v1.0 launched Feb/Mar 2025; auto-memory feature in subsequent releases; v2.1.59+ required) | 2026 (active 2026 release cadence; latest v0.6.1 2026-05-04) |
| Backend storage | file (~/.claude/projects/<project>/MEMORY.md) | SQLite (WAL mode) at ~/.cache/codebase-memory-mcp/ |
| MCP | native (first-party) — Claude Code consumes MCP | native (first-party MCP server) |
| Optimised for | Claude-Code-native + MCP-portable memory | structural code knowledge graphs (token-efficient; 99.2% reduction vs grep) + sub-ms queries + 155-language tree-sitter coverage |
| Anti-fit | not for non-Claude-Code clients (some are MCP-portable) | not for non-code memory; not for natural-language conversation memory; SEMANTICALLY_RELATED edges require optional embedding pipeline |
At a glance
| Claude Code auto-memory | codebase-memory-mcp (DeusData) | |
|---|---|---|
| Section | Claude Code memory mechanisms | Claude Code memory mechanisms |
| Tier | T1 | T1 |
| Type | Per-project file directory | Tree-sitter knowledge-graph MCP for code |
| Created | 2025-03 (Claude Code v1.0 launched Feb/Mar 2025; auto-memory feature in subsequent releases; v2.1.59+ required) | 2026 (active 2026 release cadence; latest v0.6.1 2026-05-04) |
| Latest release | — | v0.6.1 / 2026-05-04 |
| License | — | MIT |
| GitHub | — | 2.1k★ (DeusData/codebase-memory-mcp) |
| Pricing | — | free / open source (MIT); no paid tier |
| Funding | — | searched not found |
| Backend storage | file (~/.claude/projects/<project>/MEMORY.md) | SQLite (WAL mode) at ~/.cache/codebase-memory-mcp/ |
| Deployment | — | Local — single static binary (macOS arm64/amd64; Linux arm64/amd64; Windows amd64) |
| API surface | — | MCP (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 |
| Multi-tenancy | hard-isolation (per project) | — |
| MCP | native (first-party) — Claude Code consumes MCP | native (first-party MCP server) |
| A2A | not supported | not supported |
| OpenTelemetry | searched not found | searched not found |
| Optimised for | Claude-Code-native + MCP-portable memory | structural code knowledge graphs (token-efficient; 99.2% reduction vs grep) + sub-ms queries + 155-language tree-sitter coverage |
| Anti-fit | not for non-Claude-Code clients (some are MCP-portable) | not for non-code memory; not for natural-language conversation memory; SEMANTICALLY_RELATED edges require optional embedding pipeline |
Taxonomy
| Axis | Claude Code auto-memory | codebase-memory-mcp (DeusData) |
|---|---|---|
| storage | file | graph |
| retrieval | injection | structural-query |
| persistence | cross-session | project-bound |
| update | append-only | replacement |
| unit | fact | fact |
| governance | user-controllable | user-controllable |
| conflict | append | deterministic-overwrite |
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.
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.