MCP.Market

XMemo MCP server

online · 100% uptime
by yonro·io.github.yonro/xmemo·v0.4.346·13 stars

Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.

A99/100grade A
What users say
No reviews yet
Be the first
Safety scan
A99/100

full report

Adoption
Growing

13 stars40 downloads/wk

Reviews

Write one

Nobody has reviewed XMemo yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

XMemo tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan66 source files scanned25/25
  • Live reliabilityremote reachable in 562ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 99/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How XMemo compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
99/100
higher than 99% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,041 ms
faster than 10% of 30,031 servers
GitHub stars
13
more than 89% of 28,688 servers
Downloads a week
40
more than 31% of 12,191 servers with a package

Release history: 2 versions in the registry since 2026-08-13, latest 2026-09-25, typically one every 43 days.

Install XMemo in Claude Code, Cursor or VS Code

claude mcp add --transport http xmemo https://xmemo.dev/mcp
Add to Cursor

What the publisher says

From the XMemo repository's README, as published. We do not edit it. Read it on GitHub

XMemo CLI

One private memory layer for every AI agent.

Install, authenticate, diagnose, and connect XMemo across editors, CLIs, and autonomous agents from one production-ready command line.

English · 简体中文

Quick start · Integrations · Connection modes · Commands · Security

@xmemo/client is the official control plane for connecting AI tools to XMemo. It makes setup repeatable, keeps credentials out of project files, and gives every supported client a consistent path to durable, user-owned memory.

The package is deliberately small: the CLI runtime, safe client configuration, behavior profiles, XMemo skills, and marketplace metadata. Server code, databases, deployment files, logs, and internal operations remain outside the npm distribution.

Architecture

Why XMemo CLI

and smoke checks share one predictable interface.

  • One control plane — login, diagnostics, configuration, profiles, updates,

credential; it never embeds the credential value.

  • Private by design — generated project configuration references a

integrations instead of duplicating the same capability through MCP.

  • Native where it matters — OpenClaw and Hermes use dedicated memory

cover modern editors, terminals, and agent runtimes.

  • Portable everywhere else — hosted Streamable HTTP MCP and local stdio

dry-run, or explicit confirmation before making changes.

  • Safe automation — supported setup and removal paths offer preview,

file allowlist and release provenance.

  • Small supply-chain surface — the npm package is governed by an explicit

Quick start

npm install -g @xmemo/client
xmemo login
xmemo doctor
xmemo setup codex
xmemo status

Replace codex with your client. Preview a configuration before writing it:

xmemo setup cursor --dry-run

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

XMemo: common questions

Is XMemo MCP server safe?
Yes, by our scan: it is graded A (99/100). Read the XMemo safety report
How do I install XMemo?
It runs remotely at xmemo.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does XMemo need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is XMemo maintained?
The last commit was 5 days ago (2026-10-30). The latest release is v0.4.346.
Is XMemo up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of XMemo?
Servers from other publishers that do the same job: Nautilus Compass Memory MCP server, Deja Vu MCP server and Claudexor MCP server. Compare all XMemo alternatives.
How does XMemo compare with other MCP servers?
safety score 99/100 (higher than 99% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 1,041 ms (faster than 10% of 30,031 servers). Full comparison.

Alternatives to XMemo

Same job from other publishers: the closest match first, then the best rated.

All XMemo alternatives →
  • Nautilus Compass Memory
    Local-first long-term memory for AI agents, with byte-recomputable signed verification receipts.
    B
  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A
  • Claudexor
    Route coding work across Claude Code, Codex, Cursor, and OpenCode with shared context.
    A