Iai Personal Memory E… vs Mcp Agent Memory | AllMCPs
Side-by-Side Model Context Protocol Comparison
Iai Personal Memory Engine vs Mcp Agent Memory
In-depth architectural comparison of the Iai Personal Memory Engine and Mcp Agent 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
Iai Personal Memory Engine
Knowledge & Memory · Local stdio
Quality: 67/100 (Great) | Auth: No auth required
Mcp Agent Memory
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Iai Personal Memory Engine if you need specialized Knowledge & Memory tools running via a local process. Choose Mcp Agent 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 Iai Personal Memory Engine 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).
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.
Persistent agent memory via filesystem-native consolidation daemon. Agents read/write/search memory through MCP; a background daemon handles consolidation and extraction. Works with Kiro, Claude Desktop, Cursor, and any MCP client. npx mcp-agent-memory --setup
Tools & Capabilities Breakdown
Iai Personal Memory Engine Tools (9)
memory_recall
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).
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).
Iai Personal Memory Engine is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Mcp Agent Memory belongs to Knowledge & Memory using local stdio subprocess. Select Iai Personal Memory Engine when you need capabilities focused on knowledge & memory and Mcp Agent Memory when you require tools for knowledge & memory.
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.
Mcp Agent Memory Tools (4)
memory_read
Read the agent memory index (MEMORY.md) and optionally specific topic files. Call with no arguments to load only the lightweight index (cheap). Pass `topics` only when you need the full content of a specific topic file.
memory_append_session
Append a session summary to the sessions directory. The daemon will later extract durable memories from it. Call this at the end of meaningful exchanges. Keep summaries focused on durable findings and decisions (target 300-800 tokens), not play-by-play — longer summaries cost more during consolidation.
memory_search
Search memory files for a substring. Use this to recall specific facts without loading everything.
memory_daemon_status
Check whether the memory consolidation daemon is running. Reports if the daemon is not installed or not available on this platform.