Ext Ops Panel
Open dashboard
Comparison

claude-mem vs MCP AutoMem

claude-mem is a plugin bundle for AI coding tools published by Alex Newman. 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-15. 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

Where each is published
Marketplaceclaude-memMCP AutoMem
Community marketplace alamator/claude-memory Not seen in the last pass
Version: 12.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.10.0
Downloads/month (npm): 831
Downloads/week (npm): 261
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

claude-mem vs MCP AutoMem
Factclaude-memMCP AutoMem
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)65 (better)
Forks (GitHub) (differs)0 (worse)15 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@verygoodplugins/mcp-automem)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)92
Parts of the bundle (differs)157
Licence (differs)AGPL-3.0MIT
Repository (differs)github.com/alamator/claude-memorygithub.com/verygoodplugins/mcp-automem
Changes in the last 7 days22
First seen (differs)2026-10-142026-10-11

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

claude-mem

In its own words, on Community GitHub marketplaces:

Persistent memory system for Claude Code - context compression across sessions

MCP AutoMem

In its own words, on Official MCP Registry:

Graph-vector memory for AI assistants using FalkorDB and Qdrant

How to run each

claude-mem As a Claude Code plugin

Claude Code
/plugin marketplace add alamator/claude-memory
/plugin install claude-mem@thedotmack

MCP AutoMem As a Claude Code plugin

Claude Code
/plugin marketplace add verygoodplugins/mcp-automem
/plugin install automem@verygoodplugins-mcp-automem

Commands 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: claude-mem · 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.

Where the data comes from: how the catalog is built