User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like XMemo.
https://xmemo.dev/mcpnpx -y @xmemo/clientHeaders: Authorization, X-Memory-OS-Agent-ID, X-Memory-OS-Agent-Instance-ID
Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-yonro-xmemo": {
"command": "npx",
"args": [
"-y",
"@xmemo/client"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Paste an API key, bearer token, or session value from the provider. It is used once to list inventory and discarded after the request.
Bearer token issued by XMemo; send as an Authorization Bearer value.
Optional stable agent family id for attribution, for example 'claude-code' or 'copilot-cli'.
Optional stable local installation id for attribution; XMemo hashes it server-side.
XMemo is an MCP server for User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.. It supports STDIO, HTTP transport.
Use the generated config in Install. This server runs with npx -y @xmemo/client; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://xmemo.dev/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://xmemo.dev/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://xmemo.dev/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://xmemo.dev/mcp.
XMemo uses STDIO, HTTP transport. Endpoint: https://xmemo.dev/mcp.
XMemo inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
XMemo is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
@xmemo/clientstdio | npm | 0.4.163 | None advertised |