Kumbuka vs XMemo for OpenClaw

A side-by-side look at the Kumbuka 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.

Kumbuka logoKumbukaKnowledge & Memory · Remote HTTP/SSEGoverned, auditable knowledge your team curates for its AI assistants, self-hostable60GoodAuth: oauth 2.0XMemo for OpenClaw logoXMemo for OpenClawKnowledge & Memory · Remote HTTP/SSENative XMemo cloud-memory provider for OpenClaw agents: long-term memory, semantic recall, TODOs, snapshots, and audit tools.60GoodAuth: api key required

Verdict: choose Kumbuka for knowledge & memory work over a hosted endpoint; 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?

Kumbuka logoChoose Kumbuka when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like memory_remember, memory_recall, memory_forget.
Explore Kumbuka

XMemo for OpenClaw logoChoose 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.
Explore XMemo for OpenClaw

Feature & specification comparison

Rows where the two servers differ are marked.

SpecKumbuka logoKumbukaXMemo for OpenClaw logoXMemo for OpenClaw
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal60/100 · Good60/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthOAuth 2.0API key required
PricingNot declaredNot declared
Required env varsNone listedXMEMO_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars12
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools515

Tools & capabilities

Kumbuka tools 5

  • memory_rememberWrite or append an entry (upsert on `key`). Caller picks `scope`, `type`, optional `key`.
  • memory_recallRead entries with filters: `scope`, `type`, substring `query`, optional `include_global`.
  • memory_forgetRemove an entry by `id` or by `(scope, key)`.
  • memory_scopesList the scopes the caller may see (their private scope plus shared ones).
  • memory_load_contextA typed, ready-to-inject digest of the relevant rules, grouped by type.

XMemo for OpenClaw tools 15

  • memory_searchSemantic recall across visible XMemo memory
  • memory_getFetch an exact memory by reference
  • memory_storeSave durable memory
  • memory_forgetDelete an exact memory
  • xmemo_memory_listBrowse or search memories using query/path hints
  • xmemo_memory_updateUpdate an existing memory
  • xmemo_todo_createCreate a durable TODO
  • xmemo_todo_listList TODOs
  • xmemo_todo_completeComplete a TODO
  • xmemo_record_eventRecord a timeline event or milestone
  • xmemo_restart_snapshot_saveSave restart/handoff state
  • xmemo_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.

Kumbuka

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kumbuka-2": {
      "command": "npx",
      "args": [
        "-y",
        "kumbuka-2"
      ]
    }
  }
}

XMemo for OpenClaw

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "xmemo-openclaw-memory": {
      "url": "https://xmemo.dev/mcp"
    }
  }
}

Frequently asked questions

Kumbuka is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. XMemo for OpenClaw belongs to Knowledge & Memory and uses a remote HTTP/SSE transport. Pick Kumbuka 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.

Kumbuka has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 kumbuka-2 and xmemo-openclaw-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Kumbuka has a quality signal of 60/100 (Good) with 0 views, 0 installs and 1 GitHub stars. XMemo for OpenClaw has 60/100 (Good) with 1 views, 0 installs and 2 GitHub stars.