Mneme

Mneme architecture What runs on your machine.

Four layers, from your AI host down to the store on your disk. Twenty-seven courses of stone in this well, one for each storage layer. Go down with the light.

  1. i · AI hostClaude Code, Cursor and the others
  2. ii · MCP wireJSON-RPC 2.0 over stdio
  3. iii · The daemonRust, watching your code
  4. iv · The store27 layers of SQLite, on your disk

Layer i · the AI host

Claude, Cursor, and the rest.

Claude Code, Cursor, Codex, Windsurf, Zed, Gemini, Qwen and Claude Desktop all speak MCP. Mneme registers as a stdio server with each of them, and one daemon serves every client at once: open three editors and they share one memory.

Layer ii · the MCP wire

A standard protocol. Just stdio.

The Model Context Protocol, JSON-RPC 2.0 over stdio, with the AI host’s own process. Through it Mneme offers 49 tools: find_references, call_graph, blast_radius, recall_concept, audit_corpus and more.

Claude Code hooks guide the agent too: a reminder on each prompt, a blast-radius check before an edit, and a hint toward a structural search before a plain Grep.

Layer iii · the daemon

A Rust supervisor that keeps watch.

A long-running Rust process with a watchdog that restarts it. Symbol resolvers for Rust, TypeScript and Python. A BGE embedder that runs on your CPU through ONNX Runtime. A file watcher that rebuilds the part of the graph an edit touched, in under a second. Audit scanners for security, performance, accessibility and drift run on a schedule.

One round trip of blast_radius("handleLogin") takes under 20 ms at the 95th percentile.

Layer iv · the store

Twenty-seven layers. One disk.

Sharded SQLite with WAL, full-text search and automatic vacuum, at ~/.mneme. The schema only moves forward, so your graph survives every upgrade. A diff of the graph between commits, and five export formats.

  • Graph
  • History
  • ToolCache
  • Tasks
  • Semantic
  • Git
  • Memory
  • Errors
  • Multimodal
  • Deps
  • Tests
  • Perf
  • Findings
  • Agents
  • Refactors
  • Contracts
  • Insights
  • LiveState
  • Telemetry
  • Corpus
  • Audit
  • Wiki
  • Architecture
  • Conventions
  • Federated
  • Concepts
  • Meta

Privacy by design

It stays in the house.

  • Your source codeParsed on your machine. The syntax trees and the graph live in SQLite on your disk.
  • EmbeddingsComputed on your CPU through ONNX Runtime and kept in the store.
  • The wireMCP runs over stdio. The daemon listens on 127.0.0.1 only and checks the origin of each request.
  • Updatesmneme self-update downloads a new binary, checks its health after the swap, and puts the old one back if the check fails.
  • FederationOff until you turn it on. Then it shares fingerprints of code structure between machines you control, never the source itself.