Claude Code auto-memory vs Official MCP Memory server
Claude Code auto-memory vs Official MCP Memory server: 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 | Official MCP Memory server | |
|---|---|---|
| Capability band | competent | entry |
| Capability composite | 70 | 35 |
| 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, Multi Agent Coordination |
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 | Official MCP Memory server | |
|---|---|---|
| Capability band | competent | entry |
| Capability composite | 70 | 35 |
| Use cases | Code Generation Focused, Long Running Session, Offline Capable | Code Generation Focused, Long Running Session, Offline Capable, Multi Agent Coordination |
| Type | Per-project file directory | KG-based persistent memory MCP |
| Created | 2025-03 (Claude Code v1.0 launched Feb/Mar 2025; auto-memory feature in subsequent releases; v2.1.59+ required) | 2024-11 |
| Backend storage | file (~/.claude/projects/<project>/MEMORY.md) | file (JSON) |
| MCP | native (first-party) — Claude Code consumes MCP | native (first-party) — reference implementation |
| OpenTelemetry | searched not found | no |
At a glance
| Claude Code auto-memory | Official MCP Memory server | |
|---|---|---|
| Section | Claude Code memory mechanisms | Claude Code memory mechanisms |
| Tier | T1 | T1 |
| Type | Per-project file directory | KG-based persistent memory MCP |
| Created | 2025-03 (Claude Code v1.0 launched Feb/Mar 2025; auto-memory feature in subsequent releases; v2.1.59+ required) | 2024-11 |
| Latest release | — | 2026.8.31 (2026-08-31) — @modelcontextprotocol/server-memory@2026.8.31 |
| License | — | Apache-2.0 AND MIT (new contributions Apache-2.0; legacy code MIT; docs CC-BY-4.0) |
| GitHub | — | modelcontextprotocol/servers — ~90.0k stars, last release 2026-08 |
| Pricing | — | free / open source (Apache-2.0 / MIT) |
| Backend storage | file (~/.claude/projects/<project>/MEMORY.md) | file (JSON) |
| Deployment | — | local (Node.js MCP server; local JSON file) |
| API surface | — | MCP (stdio); knowledge-graph tools (create_entities/relations/observations, read/search/delete) |
| Multi-tenancy | hard-isolation (per project) | — |
| MCP | native (first-party) — Claude Code consumes MCP | native (first-party) — reference implementation |
| A2A | not supported | not supported |
| OpenTelemetry | searched not found | no |
| 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 | Official MCP Memory server |
|---|---|---|
| storage | file | graph |
| retrieval | injection | graph-traversal |
| persistence | cross-session | cross-session |
| update | append-only | overwrite |
| unit | fact | fact |
| governance | user-controllable | inspectable |
| conflict | append | llm-arbitrate |
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.
Official MCP Memory server
Pros: Reference implementation in the MCP spec; smallest possible memory primitive — useful for testing and lightweight cases.
Cons: Minimal feature set — no extraction, no governance, no retention policy; production deployments quickly outgrow it.