mem0 vs EvolutionDB Long-Term Memory
mem0 is a plugin bundle for AI coding tools published by mem0ai. 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-13. 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
| Marketplace |  mem0 | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 54a03cc Forks (GitHub): 7 884 Stars (GitHub): 67 055 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
| Fact | mem0 | EvolutionDB Long-Term Memory |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 67 055 | No figure on GitHub |
| Forks (GitHub) (differs) | 7 884 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mcp-server-evolutiondb) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 7, secrets among them: 1 |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mem0ai/mem0 | github.com/alptekin/evolutiondb |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
mem0
Connect Mem0 to Claude to give your agent persistent memory across sessions. Claude can store user preferences, project context, and conversation history, then search, update, or forget them as new information comes in. Useful for coding assistants that remember your codebase conventions, support agents that recall customer history, research workflows that build context over weeks, or any use case where Claude resets back to zero today. Memories are scoped per user, agent, or session. Cloud-hosted, no local install.
EvolutionDB Long-Term Memory
Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.
How to run each
mem0 As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mem0@claude-communityEvolutionDB Long-Term Memory As a local MCP server: PyPI package
claude mcp add --env "EVOSQL_PASSWORD=<YOUR_EVOSQL_PASSWORD>" --env "MCP_USER_ID=<YOUR_MCP_USER_ID>" --transport stdio evolutiondb-memory -- uvx mcp-server-evolutiondbRequires: 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 mem0 publish no settings it asks for, so we do not compare settings.
What it can do: mem0 · 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.