In-depth architectural comparison of the YourMemory and Iai Personal Memory Engine 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
YourMemory
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Iai Personal Memory Engine
Knowledge & Memory · Local stdio
Quality: 67/100 (Great) | Auth: No auth required
Verdict Summary: Choose YourMemory if you need specialized Knowledge & Memory tools running via a local process. Choose Iai Personal Memory Engine 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 YourMemory 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: Ebbinghaus forgetting-curve memory decay and pruning, Hybrid retrieval combining BM25, vector embeddings, and entity graph, Consolidation of related facts into summaries to reduce bloat.
Persistent memory for AI agents with Ebbinghaus forgetting-curve decay, hybrid BM25+vector retrieval, and entity graph for multi-hop reasoning. Memories auto-prune by importance and recall rate. Built-in browser dashboard, multi-agent support, and yourmemory ask for zero-API-call local queries. pip install yourmemory
Local memory daemon for any MCP-over-stdio client with three-tier storage (episodic/semantic/procedural). Own SQLite + hnswlib store (Hippo) with bge-small-en-v1.5, MIT-licensed community-detection reranking (MOSAIC), and sleep-cycle consolidation. AES-256-GCM encrypted at rest, no telemetry. Verbatim recall >=99% and post-contradiction Rescue@10 1.000 at honest scale. Ambient capture via shell hooks. Windows support in beta.
Tools & Capabilities Breakdown
YourMemory Tools (6)
Ebbinghaus forgetting-curve memory decay and pruning
Hybrid retrieval combining BM25, vector embeddings, and entity graph
Consolidation of related facts into summaries to reduce bloat
Tamper-evident hash-chained audit trail of memory operations
Role-based team memory pools with privacy controls
Local-first operation with zero API key requirement
Iai Personal Memory Engine Tools (9)
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).
YourMemory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Iai Personal Memory Engine belongs to Knowledge & Memory using local stdio subprocess. Select YourMemory when you need capabilities focused on knowledge & memory and Iai Personal Memory Engine when you require tools for knowledge & memory.
Cue-based recall — returns hits **and anti-hits**: memories that *contradict* the cue surface next to the ones that match, so a stale fact can't masquerade as current.
memory_temporal_recall
Time-anchored recall — *"what did I say about pricing in May?"*
memory_recall_structural
Retrieve by the *shape* of a memory (the HD substrate), not just its embedding.
memory_search
Plain text search over the store.
memory_capture
Write a memory explicitly (ambient capture normally does this for you).
memory_contradict
Record that a fact changed. The old version is archived, not erased — both stay retrievable. That's the Rescue@10 and historical-verbatim story in the [benchmarks](#benchmarks).
memory_reinforce
Strengthen a memory's recall pathways.
memory_consolidate
Run a consolidation pass now instead of waiting for idle.
profile_get_set
The eleven sealed procedural knobs the engine learns about you.