claude-mem vs Official MCP Memory server
claude-mem 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-mem | Official MCP Memory server | |
|---|---|---|
| Capability band | competent | entry |
| Capability composite | 55 | 35 |
| Cost tier | free | free |
| $/Mtok input | 0 | 0 |
| $/Mtok output | 0 | 0 |
| Use cases | Code Generation Focused, Long Running Session | Code Generation Focused, Long Running Session, Offline Capable, Multi Agent Coordination |
Where they differ (13)
Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.
| claude-mem | Official MCP Memory server | |
|---|---|---|
| Capability band | competent | entry |
| Capability composite | 55 | 35 |
| Use cases | Code Generation Focused, Long Running Session | Code Generation Focused, Long Running Session, Offline Capable, Multi Agent Coordination |
| Type | Episodic / session-log compression | KG-based persistent memory MCP |
| Created | 2025-09 | 2024-11 |
| Latest release | v12.7.0 2026-05-06 | 2026.1.26 2026-01-27 |
| License | AGPL-3.0 | Custom |
| GitHub | 72.7k★ +9.1k/mo TypeScript | 85.1k★ +4.8k/mo TypeScript |
| Pricing | free / open source (AGPL-3.0); no paid tier | free / open source (MIT) |
| Backend storage | searched not found | file (JSON) |
| Deployment | local — SQLite + FTS5 per project; optional Chroma vector; no cloud | local (Node.js MCP server; local JSON file) |
| API surface | searched not found | MCP (stdio); knowledge-graph tools (create_entities/relations/observations, read/search/delete) |
| MCP | native (first-party) | native (first-party) — reference implementation |
At a glance
| claude-mem | Official MCP Memory server | |
|---|---|---|
| Section | Claude Code memory mechanisms | Claude Code memory mechanisms |
| Tier | T1 | T1 |
| Type | Episodic / session-log compression | KG-based persistent memory MCP |
| Created | 2025-09 | 2024-11 |
| Latest release | v12.7.0 2026-05-06 | 2026.1.26 2026-01-27 |
| License | AGPL-3.0 | Custom |
| GitHub | 72.7k★ +9.1k/mo TypeScript | 85.1k★ +4.8k/mo TypeScript |
| Pricing | free / open source (AGPL-3.0); no paid tier | free / open source (MIT) |
| Backend storage | searched not found | file (JSON) |
| Deployment | local — SQLite + FTS5 per project; optional Chroma vector; no cloud | local (Node.js MCP server; local JSON file) |
| API surface | searched not found | MCP (stdio); knowledge-graph tools (create_entities/relations/observations, read/search/delete) |
| Embedding | searched not found | — |
| Multi-tenancy | searched not found | — |
| MCP | native (first-party) | native (first-party) — reference implementation |
| A2A | not supported | not supported |
| OpenTelemetry | no | 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-mem | Official MCP Memory server |
|---|---|---|
| storage | file | graph |
| retrieval | injection | graph-traversal |
| persistence | cross-session | cross-session |
| update | consolidation | overwrite |
| unit | summary | fact |
| governance | inspectable | inspectable |
| conflict | append | llm-arbitrate |
Pros & cons
claude-mem
Pros: OSS plugin that adds auto-memory + indexing without sending data to Anthropic's cloud — strongest privacy posture for Claude Code memory.
Cons: Plugin install + maintenance burden; less polished than first-party auto-memory.
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.