Ext Ops Panel
Open dashboard
Comparison

memstack vs MCP AutoMem

memstack is a plugin bundle for AI coding tools published by cwinvestments. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, 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-20. 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
MarketplacememstackMCP AutoMem
Claude Code: claude-plugins-community Listed
Version: 3.7.0
Forks (GitHub): 45
Stars (GitHub): 425
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

memstack vs MCP AutoMem
FactmemstackMCP AutoMem
Marketplaces that list it22
Stars (GitHub) (differs)425 (better)65 (worse)
Forks (GitHub) (differs)45 (better)15 (worse)
Last release (differs)2026-10-19 (worse)2026-10-20 (better)
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)62
Parts of the bundle (differs)917
LicenceMITMIT
Repository (differs)github.com/cwinvestments/memstackgithub.com/verygoodplugins/mcp-automem
Changes in the last 7 days33
First seen2026-10-112026-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

memstack

In its own words, on Claude Code: claude-plugins-community:

100 battle-tested skills for Claude Code across 10 categories: session memory, git workflows, database migrations, security scanning, deployments, API development, frontend, content/marketing, business docs, and DevOps. Auto-trigger commands fire based on what you're working on. Session handoffs preserve context across conversations. One install deploys across all your projects. 77 free skills included, 23 Pro-exclusive available at memstack.pro.

MCP AutoMem

In its own words, on Official MCP Registry:

Graph-vector memory for AI assistants using FalkorDB and Qdrant

How to run each

memstack As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install memstack@claude-community

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: memstack · What it can do: MCP AutoMem · 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.

Where the data comes from: how the catalog is built