In-depth architectural comparison of the Lean Memory and Memory Arbiter MCP 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: 55/100 (Good) | Auth: No auth required
Memory Arbiter MCP
Knowledge & Memory · Remote HTTP/SSE
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Lean Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Memory Arbiter MCP if your workspace requires Knowledge & Memory integration with remote web transport. 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.
Lean Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memory Arbiter MCP belongs to Knowledge & Memory using remote streaming HTTP/SSE transport. Select Lean Memory when you need capabilities focused on knowledge & memory and Memory Arbiter MCP when you require tools for knowledge & memory.
Explicit user-authorized governance: retire a whole memory, resolve a conflict, confirm a memory, correct a judgment, and govern workspace aliases / pending workspaces. Do not use for ordinary updates.
memory_repair
Maintenance and repair: split, rebuild claims/embeddings, cleanup, vector resync, entity backfill, and pending activation. Prefer dry-run first.
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]'
AI enhancement middleware: precise retrieval replaces full-memory loading (80%+ token cut), rule-based conflict arbitration with explainable reasons, and one local SQLite shared across Claude Code/Codex/Cursor/ZCode. Local-first, zero cloud, MIT. pip install memory-arbiter-mcp