Memory (reference) vs Engram
Both are memory & reasoning MCP servers, and we ran both through the same test (recall across sessions) in each app. Memory (reference) passed 4 of 4 apps we tested it in; Engram passed 2 of 4.
Test results side by side
| Memory (reference) | Engram | |
|---|---|---|
| Claude Code | Passed 2026-10-19 | Partial 2026-10-15 |
| Cursor | Passed 2026-10-19 | Partial 2026-10-15 |
| Claude Desktop | Passed 2026-10-21 | Passed 2026-10-21 |
| ChatGPT (Codex) | Passed 2026-10-20 | Passed 2026-10-21 |
| Tools exposed (protocol check) | 9 tools | 22 tools |
| GitHub stars | 91,266 (shared repo) | 7,201 |
| License | NOASSERTION | MIT |
| Last push | 2026-10-13 | 2026-10-14 |
Results from our own harness runs, dated per cell. Stars and last push from GitHub at our last data refresh. We don’t pick a winner here: which one fits depends on your app and setup.
What each does
Memory (reference): A simple knowledge-graph memory the agent can add to and search across sessions, stored in a local JSON file.
Engram: Persistent memory for coding agents: a Go binary storing memories in SQLite with full-text search over MCP.
