Ext Ops Panel
Open dashboard
Comparison

mem9 vs EvolutionDB Long-Term Memory

mem9 is a plugin bundle for AI coding tools published by mem9-ai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-28. 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
Marketplacemem9EvolutionDB Long-Term Memory
Community marketplace mem9-ai/mem9 Listed
Version: 0.3.4
Forks (GitHub): 125
Stars (GitHub): 1 233
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

mem9 vs EvolutionDB Long-Term Memory
Factmem9EvolutionDB Long-Term Memory
Marketplaces that list it11
Stars (GitHub) (differs)1 233No figure on GitHub
Forks (GitHub) (differs)125No 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)5Not published
Parts of the bundle (differs)8Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/mem9-ai/mem9github.com/alptekin/evolutiondb
Changes in the last 7 days (differs)20
First seen (differs)2026-10-282026-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

mem9

In its own words, on Community GitHub marketplaces:

Persistent cloud memory for Claude Code with automatic recall, transcript ingest, and on-demand setup, recall, and store skills.

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

mem9 As a Claude Code plugin

Claude Code
/plugin marketplace add mem9-ai/mem9
/plugin install mem9@mem9

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 mem9 publish no settings it asks for, so we do not compare settings.

What it can do: mem9 · What it can do: EvolutionDB Long-Term Memory · 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