agent-memory vs XMemo
agent-memory is a plugin bundle for AI coding tools published by Keshab0310. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). XMemo is an MCP server published by yonro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  agent-memory |  XMemo |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.0 Forks (GitHub): 2 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.346 Downloads/month (npm): 1 758 Downloads/week (npm): 64 Forks (GitHub): 1 Stars (GitHub): 12 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | agent-memory | XMemo |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 (worse) | 12 (better) |
| Forks (GitHub) (differs) | 2 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (xmemo.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 2, secrets among them: 1 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/keshab0310/agent-memory | github.com/yonro/memory-os-cli |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-13 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
agent-memory
Save 60-90% on LLM token costs with intelligent memory compression. agent-memory automatically compresses tool output into structured observations, shares context across agents via a memory bus, and injects only relevant memory into each prompt — keeping your token budget under control. Features: auto-compression hooks (PostToolUse), token-budgeted context injection (SessionStart), semantic search via FTS5, cross-session persistence, and a token economics dashboard showing compression ratios and savings.
XMemo
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
How to run each
agent-memory As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agent-memory@claude-communityXMemo As a remote MCP server
claude mcp add --transport http xmemo https://xmemo.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: XMEMO_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only XMemo has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only agent-memory asks for
AGENT_MEMORY_DATAPYTHONPATH
Only XMemo asks for
XMEMO_KEY (secret)XMEMO_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: agent-memory · What it can do: XMemo · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.