XMemo

listing.by

Store and recall long-term agent memory, project context and session state shared across AI clients and sessions.

state.auth.long (state.auth.title)Streamable HTTP

listing.connect

listing.explain.oauth

https://xmemo.dev/mcp

listing.note.oauth

listing.share.h

listing.share.p

mcp.tc/i/xmemo

listing.about

XMemo is a user-owned memory layer for AI agents. It stores durable facts and preferences, recalls focused context with token-budget controls, keeps project-scoped decisions and TODOs, and saves restart snapshots so agents can resume work. Each memory record carries agent identity and provenance, and access is governed by scopes.

It runs as a hosted Streamable HTTP endpoint at https://xmemo.dev/mcp with OAuth sign-in (scopes memory:read, memory:write, knowledge:read, knowledge:write), or locally through the @xmemo/client npm package, which provides an xmemo-mcp stdio server. A bearer token can be used instead of OAuth. The same memory is also reachable through a CLI and a REST API.

listing.can

  • Store, search, list and soft-delete durable memories across sessions
  • Recall focused context with token-budget controls
  • Save and restore session state and restart snapshots
  • Track project-scoped facts, TODOs and decisions
  • Attribute memories to an agent, instance and device
  • Share the same memory between several MCP clients
  • Read and write knowledge bases where enabled for the account

listing.tools

listing.notools.oauth

listing.prompts

  • Remember that this project uses pnpm and Node 20.

  • Recall what we decided about the database schema last week.

  • Save a restart snapshot of my current work before I close this session.

  • Add a TODO to the project memory to update the API docs.

listing.setup.h

listing.setup.oauth

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http xmemo https://xmemo.dev/mcp
  1. Start Claude Code, type /mcp, pick xmemo and choose Authenticate. A browser window opens for the yonro sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it XMemo and paste this URL:
https://xmemo.dev/mcp
  1. Click Add, then Connect, and sign in when yonro asks.

Claude Desktop's JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://xmemo.dev/mcp and click Add.
  2. Click Connect and sign in when yonro asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://xmemo.dev/mcp as the server URL and choose OAuth. ChatGPT sends you to yonro to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "xmemo": {
      "url": "https://xmemo.dev/mcp"
    }
  }
}

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"xmemo","type":"http","url":"https://xmemo.dev/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "xmemo": {
      "type": "http",
      "url": "https://xmemo.dev/mcp"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "xmemo": {
      "serverUrl": "https://xmemo.dev/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add xmemo --url https://xmemo.dev/mcp
codex mcp login xmemo

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.xmemo]
url = "https://xmemo.dev/mcp"

Gemini CLI

gemini mcp add --transport http xmemo https://xmemo.dev/mcp

Then, inside Gemini CLI, run /mcp auth xmemo to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI's settings file.

{
  "mcpServers": {
    "xmemo": {
      "type": "http",
      "url": "https://xmemo.dev/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://xmemo.dev/mcp.

listing.faq

Can I paste mcp.tc/i/xmemo into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://xmemo.dev/mcp, so your client talks to XMemo directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does XMemo need an API key or a sign-in?

Yes, you need a yonro account. The first time your client connects, it opens yonro's sign-in page. The token goes straight to the server's own URL, never through mcp.tc.

Is XMemo a remote or a local server?

Remote. yonro hosts it at https://xmemo.dev/mcp, and it speaks Streamable HTTP. There's nothing to install.

What can XMemo do?

You can store, search, list and soft-delete durable memories across sessions, recall focused context with token-budget controls and save and restore session state and restart snapshots.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc's robot read XMemo's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![XMemo on mcp.tc](https://mcp.tc/i/xmemo/badge.svg)](https://mcp.tc/i/xmemo)
HTML
<a href="https://mcp.tc/i/xmemo"><img src="https://mcp.tc/i/xmemo/badge.svg" alt="XMemo on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/xmemo.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/xmemo" title="XMemo on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json

https://mcp.tc/i/xmemo.json

listing.em.fields

listing.disclaimer_checked