Ext Ops Panel
Open dashboard
Comparison

Memex — Local AI Memory vs EvolutionDB Long-Term Memory

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). EvolutionDB Long-Term Memory is an MCP server published by alptekin. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceMemex — Local AI MemoryEvolutionDB Long-Term Memory
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.17.0
No figure published
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

Memex — Local AI Memory vs EvolutionDB Long-Term Memory
FactMemex — Local AI MemoryEvolutionDB Long-Term Memory
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-server-evolutiondb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published7, secrets among them: 1
Hooks it runs (differs)4Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/shvmvrshny/memexgithub.com/alptekin/evolutiondb
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

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.

EvolutionDB Long-Term Memory

In its own words, on Official MCP Registry:

Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.

How to run each

Memex — Local AI Memory As a Claude Code plugin

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

EvolutionDB Long-Term Memory As a local MCP server: PyPI package

Claude Code
claude mcp add --env "EVOSQL_PASSWORD=<YOUR_EVOSQL_PASSWORD>" --env "MCP_USER_ID=<YOUR_MCP_USER_ID>" --transport stdio evolutiondb-memory -- uvx mcp-server-evolutiondb

Requires: EVOSQL_PASSWORD (secret), MCP_USER_ID

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

The marketplaces of Memex — Local AI Memory publish no settings it asks for, so we do not compare settings.

What it can do: Memex — Local AI Memory · What it can do: EvolutionDB Long-Term Memory · 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 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