Memory and knowledge · MCP server
XMemo: MCP server, setup and security
XMemo is an open-source MCP server published on GitHub that lets an AI agent save search and recall scoped memories across different AI tools. Its repository has 12 stars and its last commit is from October 24, 2026 and it is licensed under MIT.
What XMemo does
According to its repository: “XMemo: user-owned agent memory to save, search, recall and manage scoped memories across AI tools.”
The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. XMemo is listed under Memory and knowledge, a category of 250 servers in the directory, where it ranks #183 by stars.
Topics declared by the repository: ai-memory, streamable-http, agent-memory, ai-agents, cli, llm-memory.
Installing and connecting XMemo
Distribution modes declared in the official MCP registry:
- npm package (Node.js, usually started with
npx) - remote server (streamable-http): you connect to it by URL, with nothing to install locally
It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: TypeScript.
The registry lists one secret variable to provide (API key, access token). Keep them in the client's environment variables, never in a shared file or a repository.
Security: what to check
Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.
Points found for XMemo:
- Secrets: the server acts with your credentials. Create a dedicated key with minimum rights and an expiry date.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on May 6, 2026, the yonro/memory-os-cli repository has 12 stars and 1 forks, with 0 open issues. It has more stars than 29% of the servers in the directory. It received changes this month. Version published in the registry: 0.4.346 (September 25, 2026).
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
XMemo is a reasonable choice; check the points below before connecting it.
Strengths
- Active project: recent commit
- Listed in the official MCP registry
- Usable remotely, without installation
- Permissive licence (MIT)
Limitations
- Requires an API key or token
- Few visible users
Avoid if…
- You do not want to give credentials to an agent
Alternatives
- Context763.6K ★
- Basic memory4.3K ★
- Hindsight53.4K ★
- Cognee32.7K ★
- Skill Seekers15.2K ★
- Honcho7.8K ★
Learn more
Frequently asked questions
How do I install XMemo?
XMemo is distributed as npm package (Node.js, usually started with npx) and a remote server. Add it to your client's MCP configuration (Claude Desktop, Cursor, VS Code…) following the README of yonro/memory-os-cli.
Is XMemo free?
The code is published under the MIT licence and can be used free of charge. It needs an API key: the service it connects to may be paid.
Is XMemo safe?
Points to watch: secrets. Give it minimum rights and approve sensitive actions.
Is it an official server?
Nothing says so: it is a project published by yonro on GitHub. Check who maintains it before giving it access.
What are the alternatives to XMemo?
In the same category: Context7, Basic memory, Hindsight, and Cognee. Context7 and Basic memory score higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score