NMEMORY vs XMemo for OpenClaw
A side-by-side look at the NMEMORY and XMemo for OpenClaw MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose NMEMORY for knowledge & memory work; choose XMemo for OpenClaw for knowledge & memory over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose NMEMORY when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You want tools like
memory_ingest, memory_retrieve, memory_digest.
Choose XMemo for OpenClaw when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
- 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 45/100 · Fair | 60/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | XMEMO_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 5 | 15 |
| Full listing | View NMEMORY | View XMemo for OpenClaw |
Tools & capabilities
NMEMORY tools 5
memory_ingestcapture with a birth certificate: no source + anchor, no storage.memory_retrieverecall as evidence: grounded, missing_evidence, or an honest abstain.memory_digestsession-start projection: what you know, what's ready, what's blocked.memory_relatethe five edges you reach for daily, out of nine declared: supersedes, derived_from, witnesses, blocks, and `falsifies` (a disproven fact stops grounding recall, but the evidence stays). The other four — `proposes`, `part_of`, `grounded_in`, `about` — are in the tool surface below.memory_forgettombstones with audit, never silent deletion.
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
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.
NMEMORY
No confirmed install command for NMEMORY yet — follow the setup steps linked from its listing page rather than a guessed package name.
XMemo for OpenClaw
{
"mcpServers": {
"xmemo-openclaw-memory": {
"url": "https://xmemo.dev/mcp"
}
}
}
Frequently asked questions
NMEMORY is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. XMemo for OpenClaw belongs to Knowledge & Memory and uses a remote HTTP/SSE transport. Pick NMEMORY for knowledge & memory work and XMemo for OpenClaw 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. NMEMORY has no confirmed install command yet — follow its own setup instructions.
NMEMORY has no declared pricing — check the project's own site. XMemo for OpenClaw has no declared pricing — check the project's own site. Auth: api key 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 nmemory and xmemo-openclaw-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, NMEMORY has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 9 GitHub stars. XMemo for OpenClaw has 60/100 (Good) with 1 views, 0 installs and 2 GitHub stars.