Mnemo Mcp vs Lean Memory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mnemo Mcp vs Lean Memory
In-depth architectural comparison of the Mnemo Mcp 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
Mnemo Mcp
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Lean Memory
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mnemo Mcp 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 Mnemo Mcp 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: MNEMO_MCP_RCLONE_REMOTE, MNEMO_MCP_SYNC_PASSPORT_KEY, MNEMO_MCP_DB_PATH, MNEMO_MCP_LOG_LEVEL.
Primary tools included: Hybrid search combining SQLite FTS5 and semantic embeddings, Built-in Qwen3 text embedding model, Encrypted sync across machines using rclone with Passport bundles.
Persistent AI memory with SQLite hybrid search (FTS5 + semantic). Built-in Qwen3 embedding, rclone sync across machines. Zero config, no cloud, no limits.
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]'
Category & Scope
Tools & Capabilities Breakdown
Mnemo Mcp Tools (6)
Hybrid search combining SQLite FTS5 and semantic embeddings
Built-in Qwen3 text embedding model
Encrypted sync across machines using rclone with Passport bundles
Temporal decay and importance-based memory archiving
Multi-provider LLM dispatch and plugin support
Open source with no usage limits or cloud dependencies
Lean Memory 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).
Mnemo Mcp is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Lean Memory belongs to Knowledge & Memory using local stdio subprocess. Select Mnemo Mcp when you need capabilities focused on knowledge & memory and Lean Memory when you require tools for knowledge & memory.
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.