Being vs Iai Personal Memory E… — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Being vs Iai Personal Memory Engine
In-depth architectural comparison of the Being 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
Being
Knowledge & Memory · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: API Key required
Iai Personal Memory Engine
Knowledge & Memory · Local stdio
Quality: 67/100 (Great) | Auth: No auth required
Verdict Summary: Choose Being if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. 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 Being when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, ENCRYPTION_KEY.
Primary tools included: Structured SOUL personality definitions, Scene-based episodic memory with decay and consolidation, Patrol background reflection and memory processing.
Personality Runtime for AI agents — persistent memory, identity (SOUL), and relationships that travel across Claude, OpenClaw, Mistral, and any MCP client.
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.
Category & Scope
Tools & Capabilities Breakdown
Being Tools (6)
Structured SOUL personality definitions
Scene-based episodic memory with decay and consolidation
Patrol background reflection and memory processing
Ed25519 identity keys and signature chains
MCP server and REST API access
Bring-your-own LLM API key support
Iai Personal Memory Engine Tools (9)
memory_recall
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).
Being is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Iai Personal Memory Engine belongs to Knowledge & Memory using local stdio subprocess. Select Being 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.