Ext Ops Panel
Open dashboard
Comparison

Memory (Reference) vs Memex — Local AI Memory

Memory (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Memex — Local AI Memory is a plugin bundle for AI coding tools published by Shvmvrshny. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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
MarketplaceMemory (Reference)Memex — Local AI Memory
Docker MCP Catalog Listed
Version: sha256:db0c2db07a44
Forks (GitHub): 11 780
Pulls (Docker Hub): 553 917
Stars (Docker Hub): 26
Stars (GitHub): 91 180
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
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

Memory (Reference) vs Memex — Local AI Memory
FactMemory (Reference)Memex — Local AI Memory
Marketplaces that list it11
Stars (GitHub) (differs)91 180 (better)2 (worse)
Pulls (Docker Hub) (differs)553 917No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/memory)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)9Not published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published4
Parts of the bundle (differs)Not a bundle5
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/shvmvrshny/memex
Changes in the last 7 days00
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

Memory (Reference)

In its own words, on Docker MCP Catalog:

Knowledge graph-based persistent memory system.

Memex — Local AI Memory

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

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 running locally in Docker. All data stays on your machine — nothing is sent to the cloud.

How to run each

Memory (Reference) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio memory -- docker run -i --rm mcp/memory

Memex — Local AI Memory

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of Memex — Local AI Memory publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Memory (Reference) · What it can do: Memex — Local AI Memory · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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