mcpbeat Sign in

XMemo MCP Server

answering

XMemo is answering right now. Last checked 12 min ago. 274 installs a week from npm. Last commit 11 Sep 2026.

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

Installs per day peak 95 · avg 21 · +681% w/w
a month agotoday
Uptime history 47 days of history · worst day 85%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
885 ms
Response time
average over 24h
274
Installs / week
npm and PyPI

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

      state.excluded.push({ path: path.relative(root, path.join(current, entry.name)).split(path.sep).join('/'), reason: 'dependency or build directory' });
const SENSITIVE_NAMES = /(^\.env(?:\..*)?$|^\.npmrc$|^\.pypirc$|^\.netrc$|^id_(?:rsa|dsa|ecdsa|ed25519)$|secret|token|credential|private.?key|\.(?:pem|p12|pfx|key)$)/i;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add xmemo --transport http https://xmemo.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "xmemo": {
      "url": "https://xmemo.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.xmemo]
url = "https://xmemo.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "xmemo": {
      "url": "https://xmemo.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "xmemo": {
      "url": "https://xmemo.dev/mcp"
    }
  }
}

This one needs environment variables set before it will start: XMEMO_KEY (Bearer token issued by XMemo for the stdio proxy. Optional for discovery; required for tool execution.), XMEMO_URL (Optional XMemo service base URL. Defaults to https://xmemo.dev.). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://xmemo.dev/mcp streamable-http sign-in 950 ms 12 min ago

Alternatives to XMemo

same job, measured the same way
Memoir
by camgitt

Persistent memory for AI coding tools via MCP. Remembers across sessions and machines.

226 installs/wk local only
OpenAkashic
by szara7678

Shared long-term memory vault for AI agents with 20 MCP tools.

35 tools answering
polymnemo
by pcbz

Shared cross-LLM long-term memory over MCP: semantic recall, sessions, and media (pgvector).

12 tools answering
Central Intelligence
by alekseimarchenko

Persistent memory for AI agents. Store, recall, and share knowledge across sessions.

71 installs/wk local only
MemAuthority
by iasi777

Git-backed long-term memory authority for AI agents via MCP.

local only
Engrm
by dr12hes

Shared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex.

138 installs/wk local only
Goldhold
by jerrysrodz

Persistent memory for AI agents. Search, store, and recall across sessions.

30 installs/wk answering
CP Memory
by cjhuochai

Local-first, governable long-term memory for AI coding agents

747 installs/wk local only

XMemo — questions

Answers built from our own checks of this server.

Why is there no tool list for XMemo?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is XMemo working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 885 ms. The bar chart above shows every period we have measured.
How do I connect XMemo?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to XMemo?
No API key is involved. XMemo answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is XMemo?
It answers our handshake in 885 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use XMemo?
The npm package @xmemo/client was installed 274 times in the last week. Week over week that is +681%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is XMemo open source?
Yes — it is published under the MIT licence, written in JavaScript and 12 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.