Ext Ops Panel
Open dashboard
Comparison

io.github.HBarefoot/engram vs Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents

io.github.HBarefoot/engram is an MCP server published by HBarefoot. Marketplaces we read that list it: 1 (Official MCP Registry). 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). As of our marketplace pass on 2026-10-18. 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
Marketplaceio.github.HBarefoot/engramPerseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents
Official MCP Registry Listed
Version: 1.6.3
Downloads/month (npm): 256
Downloads/week (npm): 46
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
Listed, marked deprecated
Version: 2.15.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

io.github.HBarefoot/engram vs Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents
Factio.github.HBarefoot/engramPerseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents
Marketplaces that list it11
Stars (GitHub) (differs)9No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@hbarefoot/engram)On your machine (ghcr.io/perseus-computing-llc/perseus-vault:2.15.0)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/hbarefoot/engramgithub.com/perseus-computing-llc/perseus-vault
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

io.github.HBarefoot/engram

In its own words, on Official MCP Registry:

Local-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.

Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents

In its own words, on Official MCP Registry:

Local-first MCP memory server: SQLite, FTS5 and vector search, AES-256-GCM. 55 tools, no cloud.

How to run each

io.github.HBarefoot/engram As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio engram -- npx -y @hbarefoot/engram start

Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents As a local MCP server: Docker image

Claude Code
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.db

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

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

What it can do: io.github.HBarefoot/engram · What it can do: Perseus Vault (formerly Mimir/Mneme), persistent memory engine for AI agents · 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.

Where the data comes from: how the catalog is built