Mnemolith MCP server

Mnemolith

Shared memory for AI coding tools that stays true to your code.

Mnemolith (NEE-mo-lith): "memory stone." What your AI learns, carved where every tool can read it. (Why the name)

Formerly Aether Cache. If you installed aether-cache, see Moving from Aether Cache: your memories come with you.

<!-- mcp-name: io.github.anishchugh05/mnemolith -->

Website · PyPI

Claude Code, Cursor, and other AI tools each forget your project between sessions, and when they do remember things, nothing checks whether those memories are still correct. Mnemolith gives every tool one shared, local memory, and keeps it honest:

git content hash. When docker-compose.yml changes, the memory about it is retired automatically instead of being fed to your AI forever.

• Memories go stale when the code changes. Each memory is linked to the files it's about, with a snapshot of their

next to it and confusing the model. Near-identical repeats are merged.

• Contradictions get replaced, not hoarded. "We migrated to MySQL" retires "we use Postgres" instead of sitting

change since: created, seen again, went stale, confirmed, replaced.

• Every memory can explain itself. Which tool and session saved it, which file versions it was based on, and every

CLAUDE.md, so they're committed, reviewed in PRs, and visible to teammates who don't run Mnemolith.

• It works with the files you already use. Current memories sync into a managed section of AGENTS.md and

It runs entirely on your machine, on top of a database engine I wrote from scratch.

Not a Redis clone

Mnemolith started as a from-scratch rebuild of Redis in Java, then kept going. Every layer here is written from scratch, and each one does something the layer beneath it can't:

The bottom layer alone is a working Redis: redis-cli, redis-benchmark, and redis-py talk to it unchanged. The memory layer, git awareness, and MCP server are things Redis doesn't do at all.

Claude Code ─┐                       ┌─────────────────────────────────────────────┐
Cursor ──────┼─ MCP ─► mnemolith ─┼─ RESP ─► Java engine (Main.java)            │
other tools ─┘   (Python: embeddings,│          memories, HNSW vector index,       │
                  git hashing, sync) │          history, append-only file on disk  │
                                     └─────────────────────────────────────────────┘

What it looks like

The dashboard (mnemolith ui): memories whose files changed wait for a decision, with the file versions side by side.

And from your AI tool's side, a memory linked to a file, the file changes, and the next lookup catches it:

Shortened. The full README is on GitHub.