XMemo for OpenClaw vs Iai Personal Memory Engine
A side-by-side look at the XMemo for OpenClaw and Iai Personal Memory Engine MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
X
XMemo for OpenClawKnowledge & MemoryNative XMemo cloud-memory provider for OpenClaw agents: long-term memory, semantic recall, TODOs, snapshots, and audit tools.55GoodAuth: api key requiredVerdict: choose XMemo for OpenClaw for knowledge & memory work; choose Iai Personal Memory Engine for knowledge & memory. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
XChoose XMemo for OpenClaw when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
XMEMO_KEY. - You want tools like
memory_search, memory_get, memory_store.
Choose Iai Personal Memory Engine when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: No auth required.
- You want tools like
memory_recall, memory_temporal_recall, memory_recall_structural.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | X XMemo for OpenClaw | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 55/100 · Good | 60/100 · Good |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | API key required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | XMEMO_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 912 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 15 | 9 |
| Full listing | View XMemo for OpenClaw | View Iai Personal Memory Engine |
Tools & capabilities
XMemo for OpenClaw tools 15
memory_searchSemantic recall across visible XMemo memorymemory_getFetch an exact memory by referencememory_storeSave durable memorymemory_forgetDelete an exact memoryxmemo_memory_listBrowse or search memories using query/path hintsxmemo_memory_updateUpdate an existing memoryxmemo_todo_createCreate a durable TODOxmemo_todo_listList TODOsxmemo_todo_completeComplete a TODOxmemo_record_eventRecord a timeline event or milestonexmemo_restart_snapshot_saveSave restart/handoff statexmemo_restart_snapshot_restoreRestore restart/handoff state- +3 more on the listing page
Iai Personal Memory Engine tools 9
memory_recallCue-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_recallTime-anchored recall — *"what did I say about pricing in May?"*memory_recall_structuralRetrieve by the *shape* of a memory (the HD substrate), not just its embedding.memory_searchPlain text search over the store.memory_captureWrite a memory explicitly (ambient capture normally does this for you).memory_contradictRecord 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_reinforceStrengthen a memory's recall pathways.memory_consolidateRun a consolidation pass now instead of waiting for idle.profile_get_setThe eleven sealed procedural knobs the engine learns about you.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
XMemo for OpenClaw
No confirmed install command for XMemo for OpenClaw yet — follow the setup steps linked from its listing page rather than a guessed package name.
Iai Personal Memory Engine
No confirmed install command for Iai Personal Memory Engine yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
XMemo for OpenClaw is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Iai Personal Memory Engine belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick XMemo for OpenClaw for knowledge & memory work and Iai Personal Memory Engine for knowledge & memory.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
XMemo for OpenClaw has no declared pricing — check the project's own site. Auth: api key required. Iai Personal Memory Engine is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add xmemo-openclaw-memory and codeabra-iai-personal-memory-engine as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, XMemo for OpenClaw has a quality signal of 55/100 (Good) with 0 views, 0 installs and 2 GitHub stars. Iai Personal Memory Engine has 60/100 (Good) with 3 views, 0 installs and 912 GitHub stars.