Memento vs Lean Memory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Memento vs Lean Memory
In-depth architectural comparison of the Memento and Lean Memory 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
Memento
Knowledge & Memory · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Lean Memory
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Memento if you need specialized Knowledge & Memory tools running via a local process. Choose Lean Memory 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 Memento 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: MEMENTO_DB.
Primary tools included: Local SQLite-backed memory, MCP stdio transport, Structured memory read and write.
Local-first, LLM-agnostic memory layer for AI assistants.
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]'
Memento is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Lean Memory belongs to Knowledge & Memory using local stdio subprocess. Select Memento when you need capabilities focused on knowledge & memory and Lean Memory when you require tools for knowledge & memory.