In-depth architectural comparison of the Remembra 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
Remembra
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Iai Personal Memory Engine
Knowledge & Memory · Local stdio
Quality: 67/100 (Great) | Auth: No auth required
Verdict Summary: Choose Remembra 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 Remembra when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: REMEMBRA_URL, REMEMBRA_USER_ID, REMEMBRA_ASYNC_ENRICHMENT.
Primary tools included: Entity resolution and graph-aware memory recall, PII detection and AES-256-GCM encryption at rest, Verbatim source record preservation with metadata linking.
Persistent memory layer for AI agents with entity resolution, PII detection, AES-256-GCM encryption at rest, and hybrid search. 100% on LoCoMo benchmark. Self-hosted.
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
Remembra Tools (6)
Entity resolution and graph-aware memory recall
PII detection and AES-256-GCM encryption at rest
Verbatim source record preservation with metadata linking
Hallucination flagging for unverifiable facts
Hybrid semantic search with fast embedding caching
Multi-tenant remote MCP server with API key authentication
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).
Remembra 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 Remembra 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.