XMemo

Name: XMemo
Author: yonro

by yonroversion 0.4.346i★ –iComputer or cloud

Registry nameio.github.yonro/xmemo

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Search & AI memory
You need to fill in: XMEMO_KEY, Authorization

Install

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

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: XMEMO_KEY, XMEMO_URL, Authorization, X-Memory-OS-Agent-ID, X-Memory-OS-Agent-Instance-ID, X-Memory-OS-Device-ID, X-Memory-OS-Device-Label

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add --transport http xmemo https://xmemo.dev/mcp --header 'Authorization: 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'

Or run it on your computer

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "xmemo": {
      "url": "https://xmemo.dev/mcp",
      "headers": {
        "Authorization": "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"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "xmemo": {
      "type": "http",
      "url": "https://xmemo.dev/mcp",
      "headers": {
        "Authorization": "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"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

XMEMO_KEY secret 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'.

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

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

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 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account yonro, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 7251 servers in this category
Published to the registry more recently than 48% of the other 7251 servers in this category
Basic checks equal to or better than 100% of the other 7251 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 1 of 1 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: XMEMO_KEY, Authorization

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 –, and the latest version (0.4.346) reached the registry 42 days 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 in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

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

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

Context7

by upstash

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

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

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

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

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 command	`xmemo` (alias: `client`)
Local MCP command	`xmemo-mcp`
Hosted MCP	`https://xmemo.dev/mcp`
Runtime	Node.js 20 or later
License	MIT

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:

Resource	Scope	Actions	Examples
`mcp`	MCP server connection configuration	`install`, `remove`, `status`	`xmemo mcp install codex`, `xmemo mcp status`
`plugin`	Host-native extension packages	`install`, `remove`, `status`, `list`, `info`	`xmemo plugin install gemini-cli`, `xmemo plugin list`
`skill`	Agent skill scripts & documentation	`install`, `remove`, `status`, `update`	`xmemo skill install --client openclaw`
`profile`	Markdown behavior steering instructions	`install`, `remove`, `status`, `show`	`xmemo 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:

Explicit flag or argument: --client , positional client argument, or --all.
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).
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:

Build Plan: Assemble an ordered sequence of actions across resources (e.g. plugin install followed by skill configuration).
Preview: Print the entire plan (including modified paths, commands, and unified diffs) to the terminal.
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.
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

Client	Recommended command	Connection
Codex	`xmemo setup codex`	Hosted MCP + behavior profile
Cursor	`xmemo setup cursor`	Hosted MCP + Bearer Token + behavior profile
Copilot CLI	`xmemo setup copilot`	Local authenticated proxy

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

XMemo

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

XMemo: Memory OS for AI Agents

What this repository contains

Beyond MCP

XMemo CLI

Architecture

Why XMemo CLI

Quick start

Guided onboarding (xmemo init)

Manual step-by-step setup

Running with npx

Guided onboarding without global install

Install skill or run MCP stdio server

How the commands fit together

1. Unified Resource Grammar (xmemo )

2. Unified Target Resolver

3. Plan, Confirm Once, Apply (PlanRunner)

4. Declarative Client Registry

Supported integrations

Guided onboarding (`xmemo init`)

1. Unified Resource Grammar (`xmemo` )

3. Plan, Confirm Once, Apply (`PlanRunner`)