In-depth architectural comparison of the Iai Personal Memory Engine and Moxie Docs MCP 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
Moxie Docs MCP
Knowledge & Memory · Local stdio
Quality: 82/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Iai Personal Memory Engine if you need specialized Knowledge & Memory tools running via a local process. Choose Moxie Docs MCP 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.
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, Moxie Docs MCP belongs to Knowledge & Memory using local stdio subprocess. Select Iai Personal Memory Engine when you need capabilities focused on knowledge & memory and Moxie Docs MCP 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.
Moxie Docs MCP Tools (12)
moxie.get_ai_context
Compact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.
moxie.get_doc_impact
Given the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.
moxie.get_api_context
Given paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.
moxie.review_change
Self-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.
moxie.get_conventions
Discovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.
moxie.search_docs
Semantic + keyword search over generated docs, conventions, gaps, and AI context.
moxie.get_doc_gaps
Unresolved documentation gaps with severity and the paths they concern.
moxie.get_documentation_opportunities
Recommended doc work: missing docs, drift repairs, and PR templates.
moxie.get_documentation_patterns
How the repository organizes and maintains its docs (where new docs belong).
moxie.list_docs
Paginated, section-grouped table of contents of every generated doc.
moxie.propose_doc_update
Add or update a doc as part of your current change; returns the target path + Markdown to write into your branch.
moxie.propose_doc_removal
Remove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.