mneme vs MCP AutoMem
mneme is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
mneme is a plugin bundle for AI coding tools published by Onour Impram. No marketplace we read lists it any more. 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-27. 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 |  MCP AutoMem | |
|---|---|---|
| Community marketplace onourimpram/mneme | Removed on 2026-10-17 Version: 4.1.0 Forks (GitHub): 0 Stars (GitHub): 3 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): 66 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 | mnemeno longer listed · | MCP AutoMem |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 3 | 66 |
| Forks (GitHub) (differs) | 0 | 15 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@verygoodplugins/mcp-automem) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 6 | 2 |
| Parts of the bundle (differs) | 12 | 7 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/onourimpram/mneme | github.com/verygoodplugins/mcp-automem |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
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 mneme
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Persistent memory for Claude Code that survives /clear, machine switches, and team handoffs. Hosted memory backend with hybrid retrieval (vector + BM25 + RRF), Ebbinghaus temporal…
-
Persistent semantic memory for Claude Code — auto-injects relevant context at session start, captures git commits, test results, and research via hooks, and provides 30+ MCP tools…
-
Local AI memory system for Claude Code and Cursor. Remembers your preferences, decisions, and project context across sessions using a Go HTTP service and Qdrant vector database…
-
A Claude Code plugin that adds structured, categorized memory to your projects.
-
Coding Agents forget everything when a session ends. total-recall fixes that: a shared memory layer that persists across sessions, tools, and devices. Memory is organized into…
-
Persistent local memory for Claude Code — cross-session context, semantic search, zero cloud
What each says it does
mneme
Vault-native memory for Claude Code. Markdown is ground truth. Hybrid retrieval, temporal knowledge graph, zero LLM cost on Stop, token-aware adaptive context.
MCP AutoMem
Graph-vector memory for AI assistants using FalkorDB and Qdrant
How to run each
mneme
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
MCP 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.
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: mneme · 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.