Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents vs io.github.mem0ai/mem0
Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents is an MCP server published by Perseus-Computing-LLC. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mem0ai/mem0 is an MCP server published by mem0ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 | ||
|---|---|---|
| Official MCP Registry | Listed, marked deprecated Version: 2.15.0 No figure published Not marked · First seen |
Listed Version: 1.0.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 | Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents | io.github.mem0ai/mem0 |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/perseus-computing-llc/perseus-vault:2.15.0) | Remote server (mcp.mem0.ai/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/perseus-computing-llc/perseus-vault | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 307 (3 days ago) |
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
Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents
Local-first MCP memory server: SQLite, FTS5 and vector search, AES-256-GCM. 55 tools, no cloud.
io.github.mem0ai/mem0
Persistent memory for AI agents: add, search, update, and delete long-term memories.
How to run each
Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents As a local MCP server: Docker image
claude mcp add --transport stdio mimir -- docker run -i --rm -v mimir-data:/data ghcr.io/perseus-computing-llc/perseus-vault:2.15.0 serve --db /data/perseus-vault.dbio.github.mem0ai/mem0 As a remote MCP server
claude mcp add --transport http mem0 https://mcp.mem0.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.mem0ai/mem0 has a remote endpoint we check. How we check endpoints
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: Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents · What it can do: io.github.mem0ai/mem0 · Compare two other plugins
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.