XMemo for OpenClaw vs MCP External Memory
A side-by-side look at the XMemo for OpenClaw and MCP External Memory 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 MCP External Memory for knowledge & memory as a local process. 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 MCP External Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You want tools like
memory_store, memory_search, memory_get.
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 | 45/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | XMEMO_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 15 | 7 |
| Full listing | View XMemo for OpenClaw | View MCP External Memory |
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
MCP External Memory tools 7
memory_storePersist text + optional namespace/tags/metadatamemory_searchSemantic search (cosine similarity) over all memoriesmemory_getRetrieve a single memory by IDmemory_deleteDelete a memory by IDmemory_listList memories with optional namespace/tag filter + paginationmemory_statsCount of memories, namespaces, DB pathmemory_updateUpdate an existing memory
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.
MCP External Memory
{
"mcpServers": {
"mcp-external-memory": {
"command": "uvx",
"args": [
"mcp-external-memory"
]
}
}
}
Frequently asked questions
XMemo for OpenClaw is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. MCP External Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick XMemo for OpenClaw for knowledge & memory work and MCP External Memory for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. XMemo for OpenClaw has no confirmed install command yet — follow its own setup instructions.
XMemo for OpenClaw has no declared pricing — check the project's own site. Auth: api key required. MCP External Memory has no declared pricing — check the project's own site. 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 mcp-external-memory 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. MCP External Memory has 45/100 (Fair) with 3 views, 0 installs and 0 GitHub stars.