Lean Memory vs Engram — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Lean Memory vs Engram
In-depth architectural comparison of the Lean Memory and Engram MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Lean Memory
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Engram
Knowledge & Memory · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Verdict Summary: Choose Lean Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Engram if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Lean Memory when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: LM_DATA_ROOT, ANTHROPIC_API_KEY.
Primary tools included: Single SQLite file per namespace for isolated memory storage, Hybrid dense (embedding) and sparse (FTS5) search retrieval, Add-only memory history with point-in-time querying.
Embedded, local-first agent memory in a single SQLite file per namespace (vec0 + FTS5 hybrid retrieval). ADD-only history queryable as-of any past time; offline sleep-time maintenance stages dedupe/summarize/evict proposals a human reviews. No Docker, no server, no cloud key. pip install 'lean-memory[mcp]'
Local-first persistent memory for AI agents. SQLite + local embeddings (all-MiniLM-L6-v2), hybrid semantic + FTS5 recall, secret detection, and contradiction handling. 6 MCP tools (remember, recall, forget, feedback, context, status) over stdio. Zero cloud, no API keys, fully offline. Works with Claude Desktop/Code, Cursor, and Windsurf. npm install -g @hbarefoot/engram
Tools & Capabilities Breakdown
Lean Memory Tools (6)
Single SQLite file per namespace for isolated memory storage
Hybrid dense (embedding) and sparse (FTS5) search retrieval
Add-only memory history with point-in-time querying
Offline sleep-time maintenance for deduplication and summarization
MCP server bridge with tools for add, search, and clear memory
Optional real embedder, reranker, and extractor models
Engram Tools (6)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Lean Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Engram belongs to Knowledge & Memory using local stdio subprocess. Select Lean Memory when you need capabilities focused on knowledge & memory and Engram when you require tools for knowledge & memory.