Taskive MCP vs XMemo for OpenClaw
A side-by-side look at the Taskive MCP 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.
T
Taskive MCPKnowledge & Memory · Remote HTTP/SSEAI-native project management + agent memory: tasks, sprints, risk, burnout, knowledge search.42FairAuth: not declaredVerdict: choose Taskive MCP 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?
TChoose Taskive MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
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 | T Taskive MCP | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 42/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | — | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 15 |
| Full listing | View Taskive MCP | View XMemo for OpenClaw |
Tools & capabilities
Taskive MCP tools
No tool names declared yet. Check the project README from the listing page.
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.
Taskive MCP
{
"mcpServers": {
"mcp-32": {
"url": "https://taskive.ai/mcp"
}
}
}
XMemo for OpenClaw
{
"mcpServers": {
"xmemo-openclaw-memory": {
"url": "https://xmemo.dev/mcp"
}
}
}
Frequently asked questions
Taskive MCP 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 Taskive MCP 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.
Taskive MCP 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 mcp-32 and xmemo-openclaw-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Taskive MCP has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. XMemo for OpenClaw has 60/100 (Good) with 0 views, 0 installs and 2 GitHub stars.