Sessionmem vs Lean Memory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Sessionmem vs Lean Memory
In-depth architectural comparison of the Sessionmem 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
Sessionmem
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Lean Memory
Knowledge & Memory · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Sessionmem 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 Sessionmem 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).
Primary tools included: Local SQLite storage of session memories, Automatic summary generation of key session points, Context injection at the start of new sessions.
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.
Local-first memory layer for AI coding assistants. Watches your coding sessions and injects a compact summary at the start of each new session. No cloud, no account, just a SQLite file on your machine. Works with Claude Code, Cursor, Cline, Windsurf, and any other MCP host.
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
Sessionmem Tools (6)
Local SQLite storage of session memories
Automatic summary generation of key session points
Context injection at the start of new sessions
Secret redaction to scrub sensitive data before saving
Configurable retention policy for memory pruning
Compatible with multiple MCP hosts and AI tools
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).
Sessionmem is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Lean Memory belongs to Knowledge & Memory using local stdio subprocess. Select Sessionmem when you need capabilities focused on knowledge & memory and Lean Memory when you require tools for knowledge & memory.