Iai Personal Memory E… vs Genesys Memory | AllMCPs
Side-by-Side Model Context Protocol Comparison
Iai Personal Memory Engine vs Genesys Memory
In-depth architectural comparison of the Iai Personal Memory Engine and Genesys 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
Genesys Memory
Knowledge & Memory · Local stdio
Quality: 53/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 Genesys 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.
Open-source causal memory for AI agents: persistent, explainable, MCP-native memory (13 tools).
Category & Scope
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, Genesys Memory belongs to Knowledge & Memory using local stdio subprocess. Select Iai Personal Memory Engine when you need capabilities focused on knowledge & memory and Genesys 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.
Genesys Memory Tools (13)
memory_store
Store a new memory. Use `related` for writer-specified **typed** edges (`{id, type}`); `related_to` is legacy and always creates `caused_by`. Optional `category`. May return `possible_conflicts` (heuristic hints).
memory_amend
Record a correction: creates a new memory that **supersedes** an existing one. The old memory is kept (decayed in recall), not deleted.
memory_recall
Recall memories by natural language query (vector + keyword + graph spreading activation). Supports `verbosity: "concise"` for lightweight payloads.
memory_search
Filtered vector search by status, category, date (`since`), last-active date (`active_since`), or entity. Pass an **empty query** to enumerate by recency instead (no embedder needed) — with `since`/`active_since` this answers "what's new since I last looked" without knowing what to query for.
memory_traverse
Walk the causal graph from a node. Returns reachable **nodes and the edges** of the induced subgraph (`source/target/type/weight/created_by`) — a superset of the BFS tree, so paths can be reconstructed. Honors `edge_types`.
memory_explain
Explain a memory's score. Includes a `score_model` block (formula + live per-force breakdown + staleness note) and `removal_impact`.
memory_stats
Get memory system statistics
pin_memory
Pin a memory so it's never forgotten
unpin_memory
Unpin a previously pinned memory
delete_memory
Permanently delete a memory
list_core_memories
List core memories, optionally filtered by category