Mneme capabilities Six capabilities. One memory.
Mneme’s job is to know every symbol, every edge and every decision in your project, and to hand that knowledge to any MCP host that asks. This cabinet has forty-nine niches, one for each tool. The light moves to the part each capability uses.
i · Symbol resolvers
Three names. One symbol.
Resolvers for Rust, TypeScript and Python turn the names written in code into one canonical symbol each. super::spawn, manager::WorkerPool::spawn and a bare spawn imported from the same module are the same function, and Mneme knows it.
That is the difference between an agent that answers “where is this called?” and one that returns a page of near-miss text matches.
ii · Guiding hooks
A better habit, without a wall.
The AI host assumes that Grep is how you find code. Three Claude Code hooks change the habit: a reminder of the memory on every prompt, a blast-radius check before an edit, and a hint toward find_references before a Grep or a Read. The Grep hint never blocks, and if Mneme is not running the original call goes through unchanged.
iii · Fourteen views
See the shape of your code.
An agent can name a symbol. A person still wants to see the structure. The Vision app draws your graph fourteen ways: Force Galaxy, Hierarchy Tree, Sunburst, Treemap, two Sankey flows, Arc and Chord, Timeline, Heatmap Grid, Layered Architecture, Project Galaxy 3D, Test Coverage Map, Risk Dashboard and Theme Palette. On Mneme’s own repository of 17,000 nodes the first paint comes in under half a second.
iv · Forty-nine tools
Every question, as a tool.
Recall, blast radius, call graphs, audits, refactor suggestions and drift findings, each a standard MCP tool. Any client that speaks MCP gets all of them; Mneme is not a plugin for one editor.
v · Local by design
Your code stays home.
The graph lives in plain SQLite under ~/.mneme. Embeddings are computed on your CPU through ONNX Runtime. The MCP wire is stdio, and the daemon listens on 127.0.0.1 only. For teams that will not send code to someone else’s cloud, that is where adoption starts.
vi · A rebuild on every save
It keeps pace with you.
The daemon watches your tree. Save a file and the part of the graph that depends on it rebuilds in under a second: not the whole project, only the symbols the change touched. When the agent asks what changed, the answer is already current.