Itsuki Memory vs MCP AutoMem
Itsuki Memory is a plugin bundle for AI coding tools published by Itsuki. Marketplaces we read that list it: 1 (Community GitHub marketplaces). MCP AutoMem is an MCP server published by verygoodplugins. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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 |  MCP AutoMem | |
|---|---|---|
| Community marketplace 12ziyad/universal-memory-engine | Listed Version: 0.7.0 Forks (GitHub): 4 Stars (GitHub): 13 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.10.0 Downloads/month (npm): 793 Downloads/week (npm): 89 Forks (GitHub): 15 Stars (GitHub): 65 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 | Itsuki Memory | MCP AutoMem |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 13 (worse) | 65 (better) |
| Forks (GitHub) (differs) | 4 (worse) | 15 (better) |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Remote server (itsuki.app/mcp) | On your machine (@verygoodplugins/mcp-automem) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 3 | 2 |
| Parts of the bundle (differs) | 5 | 7 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/12ziyad/universal-memory-engine | github.com/verygoodplugins/mcp-automem |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | no remote endpoint we check |
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
Itsuki Memory
Persistent memory for Claude Code: save durable facts and decisions, recall them in any future session. Receipts for every write; your rules decide what is remembered.
MCP AutoMem
Graph-vector memory for AI assistants using FalkorDB and Qdrant
How to run each
Itsuki Memory As a Claude Code plugin
/plugin marketplace add 12ziyad/universal-memory-engine
/plugin install itsuki@itsuki-pluginsMCP AutoMem As a Claude Code plugin
/plugin marketplace add verygoodplugins/mcp-automem
/plugin install automem@verygoodplugins-mcp-automemCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Itsuki Memory 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Itsuki Memory · What it can do: MCP AutoMem · 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.