Midas MCP server

Midas

The local memory layer for long-horizon AI agents — remembers across sessions, keeps what's current, and won't act on stale memory.No LLM at ingest · $0 per message · fully local · every recall traces to its source.

Your AI assistant forgets everything between sessions. Midas is the memory that lives next to it, on your machine. Your coding agent remembers the decisions, conventions, and bugs from three sessions ago — without piping every message through an LLM to "extract" facts. It costs nothing per message, nothing leaves your computer, every memory traces back to the exact turn it came from, and it won't let an agent act on memory that's stale or never confirmed.

uv tool install "midas-memory[mcp,local]"   # install
midas init                                  # create the shared memory + wire up your MCP clients
# or, no Python:    npx -y midas-memory-mcp     # TypeScript port
# or, as a library: pip install "midas-memory[local]"
uv tool upgrade midas-memory   # Update Midas

Install in your agent · See the benchmarks · Complete overview · Roadmap

Why Midas

Most memory tools call an LLM to summarize every session — so you pay in tokens forever, add latency, ship every turn to a provider, and get back rewritten facts you can't audit. Midas makes the opposite bet, and that bet is what makes it cheap, private, and trustworthy:

machine, fast local ops (~tens of ms, no per-turn network round-trip).

• $0 and private by construction. No LLM at ingest or query → no API spend, nothing leaves your

so there's no extraction step that can silently hallucinate a "fact" you never said.

• You can trust what it recalls. Recall returns the verbatim source turn, not an LLM rewrite —

duplicates; selective forgetting keeps it bounded — all with no LLM.

• It stays current on its own. Typed belief revision supersedes the old value instead of piling up

memory-justified external or destructive actions unless you explicitly confirmed them — and a superseded* memory can't authorize an action at all.

• It's safe to build on. A provenance guard lets memory inform planning but **blocks

share one live memory.

• One file, many tools. Point Claude Code, Cursor, and your chat app at one SQLite file and they

failed.*

• Proven, not asserted. Every claim has a reproducible benchmark — *including the experiments that

How Midas compares

Every Midas number below is measured and reproducible from this repo; the LLM-at-ingest column reflects the structural properties of that design class (Mem0, Zep, Hindsight) and the figures documented in BENCHMARKS.md.

Shortened. The full README is on GitHub.