cogmemai-memory vs XMemo
cogmemai-memory is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
cogmemai-memory is a plugin bundle for AI coding tools published by hifriendbot. No marketplace we read lists it any more. 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-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  XMemo | |
|---|---|---|
| Community marketplace hifriendbot/cogmemai-mcp | Removed on 2026-10-22 Version: not stated Forks (GitHub): 3 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.346 Downloads/month (npm): 1 599 Downloads/week (npm): 28 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 | cogmemai-memoryno longer listed · | XMemo |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 7 | 12 |
| Forks (GitHub) (differs) | 3 | 1 |
| 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) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/hifriendbot/cogmemai-mcp | github.com/yonro/memory-os-cli |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of cogmemai-memory
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Graph-vector memory for AI assistants using FalkorDB and Qdrant
-
Persistent memory with session tracking, compaction recovery, and Memory Protocol. Gives Claude a brain that survives across sessions.
-
The bridge between Claude's working memory and Basic Memory's durable knowledge graph — session briefings, pre-compaction checkpoints, and capture reflexes
-
Active memory writing during conversation, plus manual /memory:consolidate with theme clustering, ground-truth prune, adversarial pass, and machine validator — no…
-
engram io.github.tstockham96/engram
Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.
-
Persistent memory for Claude Code with hot cache instant recall and semantic search. Give your AI assistant a second brain.
What each says it does
cogmemai-memory
Teaches Claude best practices for memory management — when to save, importance scoring, memory types, and session workflows.
XMemo
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
How to run each
cogmemai-memory
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
XMemo 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
The marketplaces of cogmemai-memory publish no settings it asks for, so we do not compare settings.
What it can do: cogmemai-memory · What it can do: XMemo · Compare two other plugins
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.