Perseus Vault (Formerly Mimir/Mneme), Persistent Memory Engine For AI Agents MCP Server

Local-first MCP memory server: SQLite, FTS5 and vector search, AES-256-GCM. 49 tools, no cloud. That is what the perseus vault (formerly mimir/mneme), persistent memory engine for ai agents mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Give your agents memory that survives the session, so they stop re-deriving what they already learned and stop repeating past mistakes. Hybrid recall (BM25 + dense + RRF), bi-temporal history, and AES-256-GCM at rest, exposed as 65 canonical MCP tools that work with any host. Legacy mimir_* and mneme_* aliases remain callable but are not counted separately. 73.8% on LongMemEval's official harness (vs Zep 63.8%, Mem0 49.0%). One binary. One file. No Docker. No Postgres. No cloud. Local-first, air-gap ready, MIT.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 5 tools. What each one is for:

• Graph — The Graph tool exposed by this server
• Journal — The Journal tool exposed by this server
• State — The State tool exposed by this server
• Lifecycle — The Lifecycle tool exposed by this server
• Quality — The Quality tool exposed by this server

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Perseus Vault (Formerly Mimir/Mneme), Persistent Memory Engine For AI Agents's toolset — Graph, Journal, State and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Perseus-Computing-LLC; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.