XMemo for OpenClaw vs Moxie Docs MCP
A side-by-side look at the XMemo for OpenClaw and Moxie Docs MCP 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 Moxie Docs MCP 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 Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: OAuth 2.0.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
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 | 76/100 · Great |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | API key required | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | XMEMO_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 2 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 40 views 25 installs 4 upvotes |
| Tools | 15 | 12 |
| Full listing | View XMemo for OpenClaw | View Moxie Docs MCP |
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
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven 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_contextGiven 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_changeSelf-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_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie Docs-tracked doc your change makes obsolete; returns the path to delete in your branch.
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.
Moxie Docs MCP
No confirmed install command for Moxie Docs MCP 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. Moxie Docs MCP belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick XMemo for OpenClaw for knowledge & memory work and Moxie Docs MCP 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. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 moxie-docs-mcp 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. Moxie Docs MCP has 76/100 (Great) with 40 views, 25 installs and 2 GitHub stars.