Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

XMemo

by yonroversion 0.4.346i★ 13iComputer or cloud
Registry nameio.github.yonro/xmemo

How to install

What it does

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

  • Connects Computer or cloud
  • Account or key Cloud: Needs Authorization, X-Memory-OS-Agent-ID, X-Memory-OS-Agent-Instance-ID, X-Memory-OS-Device-ID, X-Memory-OS-Device-Label · Local: Needs XMEMO_KEY
  • Category Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Passed 5/5 checks · What you ask goes through the maker’s server (xmemo.dev) · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude · about 5 min

You need a XMemo key (create it on the maker’s site) · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

  1. Sign up and create a XMemo key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the XMemo site ↗

  2. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · NameXMemo
    Remote MCP server URL · Addresshttps://xmemo.dev/mcp

    Under Request headers, add this name and value

    Header nameAuthorization
    ValueBearer <paste your key here>
    Header nameX-Memory-OS-Agent-ID
    Value<paste your key here>
    Header nameX-Memory-OS-Agent-Instance-ID
    Value<paste your key here>
    Header nameX-Memory-OS-Device-ID
    Value<paste your key here>
    Header nameX-Memory-OS-Device-Label
    Value<paste your key here>

    Paste the key only into the app’s field, never into a chat or to anyone

    Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add

  4. Turn it on in a chat

    +ConnectorsXMemo

  5. Try it

    Use XMemo and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using XMemo or shows a XMemo tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect XMemo yet

XMemo needs your own key to connect, but OpenAI’s help page only describes OAuth sign-in; there is no key option we could verify

What you can do instead

A · Use an app that can connect XMemo

  • You need a XMemo key (create it on the maker’s site) · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
  • You need a XMemo key (create it on the maker’s site)
  • You need a XMemo key (create it on the maker’s site)
  • You need a XMemo key (create it on the maker’s site)

B · Others in Search & AI memory that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code · about 5 min

You need a XMemo key (create it on the maker’s site)

  1. Sign up and create a XMemo key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the XMemo site ↗

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --transport http --scope user xmemo https://xmemo.dev/mcp --header 'Authorization: Bearer your-value' --header 'X-Memory-OS-Agent-ID: your-value' --header 'X-Memory-OS-Agent-Instance-ID: your-value' --header 'X-Memory-OS-Device-ID: your-value' --header 'X-Memory-OS-Device-Label: your-value'

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  4. Type /mcp in Claude Code

    You should see XMemo listed as connected

  5. Try it

    Use XMemo and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using XMemo or shows a XMemo tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor · about 5 min

You need a XMemo key (create it on the maker’s site)

  1. Sign up and create a XMemo key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the XMemo site ↗

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Fill in your key

    In the XMemo settings, Authorization, X-Memory-OS-Agent-ID, X-Memory-OS-Agent-Instance-ID, X-Memory-OS-Device-ID, X-Memory-OS-Device-Label is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  4. Open the AI chat in Cursor in Agent mode

  5. Try it

    Use XMemo and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using XMemo or shows a XMemo tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code · about 5 min

You need a XMemo key (create it on the maker’s site)

  1. Sign up and create a XMemo key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the XMemo site ↗

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Fill in your key

    In the XMemo settings, Authorization, X-Memory-OS-Agent-ID, X-Memory-OS-Agent-Instance-ID, X-Memory-OS-Device-ID, X-Memory-OS-Device-Label is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  4. Open the AI chat in VS Code in Agent mode

  5. Try it

    Use XMemo and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using XMemo or shows a XMemo tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://xmemo.dev/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use XMemo💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

Claude Code

claude mcp add --transport http --scope user xmemo https://xmemo.dev/mcp --header 'Authorization: Bearer your-value' --header 'X-Memory-OS-Agent-ID: your-value' --header 'X-Memory-OS-Agent-Instance-ID: your-value' --header 'X-Memory-OS-Device-ID: your-value' --header 'X-Memory-OS-Device-Label: your-value'

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "xmemo": {
      "url": "https://xmemo.dev/mcp",
      "headers": {
        "Authorization": "Bearer your-value",
        "X-Memory-OS-Agent-ID": "your-value",
        "X-Memory-OS-Agent-Instance-ID": "your-value",
        "X-Memory-OS-Device-ID": "your-value",
        "X-Memory-OS-Device-Label": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "xmemo": {
      "type": "http",
      "url": "https://xmemo.dev/mcp",
      "headers": {
        "Authorization": "Bearer your-value",
        "X-Memory-OS-Agent-ID": "your-value",
        "X-Memory-OS-Agent-Instance-ID": "your-value",
        "X-Memory-OS-Device-ID": "your-value",
        "X-Memory-OS-Device-Label": "your-value"
      }
    }
  }
}

Installed on your computer

Claude Code

claude mcp add --scope user xmemo --env XMEMO_KEY=your-value -- npx -y @xmemo/client mcp serve

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "xmemo": {
      "command": "npx",
      "args": [
        "-y",
        "@xmemo/client",
        "mcp",
        "serve"
      ],
      "env": {
        "XMEMO_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "xmemo": {
      "command": "npx",
      "args": [
        "-y",
        "@xmemo/client",
        "mcp",
        "serve"
      ],
      "env": {
        "XMEMO_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "xmemo": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@xmemo/client",
        "mcp",
        "serve"
      ],
      "env": {
        "XMEMO_KEY": "your-value"
      }
    }
  }
}

Values you fill in

  • XMEMO_KEY secret required env
    Bearer token issued by XMemo for the stdio proxy. Optional for discovery; required for tool execution.
  • XMEMO_URL env
    Optional XMemo service base URL. Defaults to https://xmemo.dev.
  • Authorization secret required HTTP header
    Bearer token issued by XMemo; send as an Authorization Bearer value.
  • X-Memory-OS-Agent-ID HTTP header
    Optional stable agent family id for attribution, for example 'claude-code' or 'copilot-cli'.
  • X-Memory-OS-Agent-Instance-ID HTTP header
    Optional stable local installation id for attribution; XMemo hashes it server-side.
  • X-Memory-OS-Device-ID HTTP header
    Optional stable local device id for attribution; use a non-secret machine or installation identifier.
  • X-Memory-OS-Device-Label HTTP header
    Optional human-readable local device label for attribution, for example 'MacBook Pro' or 'PC A'.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
147/wk
Connection
Computer or cloud
Transport
stdio, streamable-http
Latest versioni
0.4.346
Published to registryi
Sep 25, 2026
Code last changedi
Nov 9, 2026
Maker
yonro
Packages
npm: @xmemo/client
Website
xmemo.dev
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 14, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account yonro, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 5 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • ✓ Pass

    Endpoint responds

    Responded in 400 ms (HTTP 401)

  • ✓ Pass

    Sign-in with OAuth

    Declares OAuth sign-in, so your AI app can take you to log in

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in with Google to post

User reviews

No reviews yet

Sign in with Google to write a review

Compared with others in Search & AI memoryi

  • More stars than 93% of the other 6128 servers in this category
  • Published to the registry more recently than 44% of the other 6128 servers in this category
  • Basic checks equal to or better than 100% of the other 6128 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is XMemo safe?

It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization, X-Memory-OS-Agent-ID, X-Memory-OS-Agent-Instance-ID, X-Memory-OS-Device-ID, X-Memory-OS-Device-Label, XMEMO_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed 5 days ago, and the latest version (0.4.346) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: Context7, Codebase Memory, OpenSEO

Others in the same category

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

by upstashWidely used↓ 1.2M/wk★ 64.8KUpdated 2 days ago

Computer or cloud

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

by DeusDataWidely used↓ 16.8K/wk★ 48.6KUpdated 28 days ago

Runs on your computer

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

by every-appWidely used★ 27.6KUpdated today

Runs in the cloud✓ everyapp.com

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

XMemo: Memory OS for AI Agents

XMemo is a user-owned Memory OS for AI agents: persistent memory, project context and session continuity with agent identity, provenance and governed access, shared across AI clients through MCP, the CLI and a public REST API surface.

English · 简体中文 | Documentation · Hosted MCP

Quick start · What this repo contains · Beyond MCP · Integrations · Connection modes · Plugins · Commands · Versioning · Security


What this repository contains

  • [`@xmemo/client`](https://www.npmjs.com/package/@xmemo/client): the official xmemo CLI for setup, diagnostics, behavior profiles, and memory commands.
  • MCP distribution: hosted Streamable HTTP configuration (https://xmemo.dev/mcp) and the local xmemo-mcp stdio server.
  • XMemo Skill & native integrations: skills/xmemo for agent platforms and the native plugin index (src/plugins/index.json).
  • Marketplace and registry metadata: canonical descriptors for MCP Registry (server.json), LobeHub (lhm.plugin.json), and AI agents (context7.json).

The hosted service implementation is private.

Beyond MCP

MCP is one access surface of XMemo, not the product boundary. XMemo provides a persistent, governed memory operating layer across AI tools and agents:

  • [Persistent Memory](https://docs.xmemo.dev/docs/tools/remember): store, search, list, and soft-delete durable facts, preferences, and operational knowledge across sessions.
  • [Context Recall](https://docs.xmemo.dev/docs/tools/recall-context): retrieve focused, relevant context on demand with token-budget controls and document expansions.
  • [Session Continuity & Working State](https://docs.xmemo.dev/docs/guides/resume-and-handoff): restart snapshots and state save/restore so agents resume context across process restarts.
  • [Project Context & Decisions](https://docs.xmemo.dev/docs/concepts/projects): track project-scoped facts, TODOs, and durable decisions across agent workflows.
  • [Agent Identity & Provenance](https://docs.xmemo.dev/docs/concepts/provenance-attribution): track authorship and origin per memory record via agent instance attribution without conflating credentials.
  • [Governed Access](https://docs.xmemo.dev/docs/concepts/scopes): scoped tokens, OAuth where the client supports it, soft/hard deletion and sensitive-memory handling (governance details).
  • Native Integrations & Skill: dedicated integration for OpenClaw, Hermes, XMemo Skill (ClawHub), and DeepSeek DSH (available, released and pilot-tested; integration maturity Preview).
  • Access Surfaces: unified via Model Context Protocol, the local CLI (xmemo), and the public REST API.

*Preview: Cloud Skills; Dream (off by default); Teams (Business plan not yet available). Knowledge Bases are available where enabled for the account.*

XMemo CLI

@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

Package@xmemo/client
Primary commandxmemo (alias: client)
Local MCP commandxmemo-mcp
Hosted MCPhttps://xmemo.dev/mcp
RuntimeNode.js 20 or later
LicenseMIT

Why XMemo CLI

  • One control plane — login, diagnostics, configuration, profiles, updates, and smoke checks share one predictable interface.
  • Private by design — generated project configuration references a credential; it never embeds the credential value.
  • Native where it matters — OpenClaw and Hermes use dedicated memory integrations instead of duplicating the same capability through MCP.
  • Portable everywhere else — hosted Streamable HTTP MCP and local stdio cover modern editors, terminals, and agent runtimes.
  • Safe automation — supported setup and removal paths offer preview, dry-run, or explicit confirmation before making changes.
  • Small supply-chain surface — the npm package is governed by an explicit file allowlist and release provenance.

Quick start

Guided onboarding (xmemo init)

For an interactive first-run experience across account authentication, detected clients, agent behavior instructions, MCP server setup, skills, and plugins, run:

npm install -g @xmemo/client

xmemo init

Flags and options:

  • xmemo init --dry-run: View the full onboarding plan without performing network calls or disk writes.
  • xmemo init --yes: Automatically accept and apply all onboarding steps without interactive prompts.
  • xmemo init --json: Emit structured JSON for the plan or result envelope.
  • xmemo init --client ...: Restrict onboarding to specific clients (e.g., cursor, codex, claude-code).
  • xmemo start: Alias for xmemo init with quick-start walkthrough steps.

Global installation exposes xmemo as the primary command, and also provides client and memory-os as aliases.

Manual step-by-step setup
xmemo account login

xmemo doctor xmemo setup codex xmemo status

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

xmemo setup cursor --dry-run
Running with npx

You can also run any CLI command directly without a global install via npx @xmemo/client :

# Check version or health

npx @xmemo/client --version npx @xmemo/client doctor

Guided onboarding without global install

npx @xmemo/client init

Install skill or run MCP stdio server

npx @xmemo/client skill install npx @xmemo/client mcp serve

[!TIP]

Start with xmemo init (or xmemo account login, xmemo doctor, and xmemo setup ).

Hand-edit MCP configuration only when a client has no verified setup path.

How the commands fit together

The XMemo CLI architecture is built on four core design principles:

1. Unified Resource Grammar (xmemo )

Every integration component is a first-class resource with predictable lifecycle actions:

ResourceScopeActionsExamples
mcpMCP server connection configurationinstall, remove, statusxmemo mcp install codex, xmemo mcp status
pluginHost-native extension packagesinstall, remove, status, list, infoxmemo plugin install gemini-cli, xmemo plugin list
skillAgent skill scripts & documentationinstall, remove, status, updatexmemo skill install --client openclaw
profileMarkdown behavior steering instructionsinstall, remove, status, showxmemo profile install cursor
  • Composite commands: xmemo setup [ ...], xmemo uninstall [ ...], and xmemo status [ ] orchestrate these resources in a single step according to the client's declarative profile.
  • Backward-compatible aliases: Familiar commands such as xmemo mcp add (alias for mcp install), xmemo profile uninstall (alias for profile remove), and xmemo skill uninstall (alias for skill remove) remain fully functional and print a helpful one-line hint in interactive terminals.
2. Unified Target Resolver

When no client is explicitly passed, the CLI uses a deterministic three-tier precedence resolution model:

  1. Explicit flag or argument: --client , positional client argument, or --all.
  2. Calling agent environment: Automatically identifies the calling agent runtime when running inside an agent session (e.g., CLAUDECODE / CLAUDE_CODE_ENTRYPOINT maps to claude-code, and CODEX_THREAD_ID / CODEX_SESSION_ID maps to codex).
  3. Detected installed clients: Inspects local configuration paths and markers. If exactly one matching client is found, it is automatically selected; if multiple clients are found in interactive mode, an interactive picker is presented. The CLI never silently writes configuration to arbitrary unverified paths.
3. Plan, Confirm Once, Apply (PlanRunner)

Mutating commands follow a strict, atomic execution pattern:

  1. Build Plan: Assemble an ordered sequence of actions across resources (e.g. plugin install followed by skill configuration).
  2. Preview: Print the entire plan (including modified paths, commands, and unified diffs) to the terminal.
  3. Confirm Once: Prompt [y/N] exactly once for the entire sequence. Re-running with --yes or -y bypasses the prompt; --dry-run displays the preview without mutation.
  4. Apply Sequentially: Steps run in dependency order, stopping immediately upon first failure. Re-running an already configured client detects that all components are up to date and reports Nothing to do.
4. Declarative Client Registry

All client configurations, recipes, and capabilities are declared centrally in src/clients/registry.js. Command implementations are purely generic orchestrators with zero hardcoded client ID strings. Platforms can also be added dynamically at runtime via registerClient().

Supported integrations

ClientRecommended commandConnection
Codexxmemo setup codexHosted MCP + behavior profile
Cursorxmemo setup cursorHosted MCP + Bearer Token + behavior profile
Copilot CLIxmemo setup copilotLocal authenticated proxy

Only the beginning is shown; read the rest in the repo