Mind · MCP Bridge

Memory for the Agent You Already Use.

Eight tools. Five lines of config. Your Claude Code, Cursor, or Codex CLI reading from the same compounding graph.

Direct answer

Anvaya's MCP memory server gives any MCP-compatible agent persistent memory: Claude Code, Cursor, Codex CLI, Windsurf, and more connect with five lines of .mcp.json and get 8 tools — mind_query (PackedContext under a 4096-token budget), mind_search, mind_get_node, mind_record_change, mind_stats, session start/end, and thread retrieval. The server is your local Mind daemon (SQLite + HNSW under .anvaya/mind/), so nothing is hosted and nothing leaves your machine. Anvaya CLI itself uses faster native transports (in-process Direct under 0.5ms, Unix-socket IPC around 2ms); MCP at ~10ms is the universal bridge. One graph, every harness: record a fix in the terminal, recall it in the IDE.

The 8 Tools

A Memory API, Not a File.

Reads and writes — the agent accumulates knowledge, not just consumes it.

01mind_query (budget 4096)The main entry: natural-language query returns a PackedContext — critical nodes, patterns, fixes, concepts — capped at a 4096-token budget.

02mind_search · mind_get_nodeHybrid semantic + keyword search across the graph; full node fetch with links, confidence, and utility history.

03mind_record_changeWrite path for agents: record decisions, fixes, and outcomes so future sessions (any client) benefit.

04mind_stats · threads · sessionsGraph stats, causal thread retrieval, explicit session start/end — observability and lifecycle over one protocol.

Setup

Five Lines.

Drop in project root as .mcp.json, restart the client, query.

01mind-mcp over stdioThe server speaks MCP stdio from your local Mind daemon — no ports, no tokens, no accounts.

02Same graph everywhereSessions from CLI, IDE, and CI land in one store with per-project isolation and cross-project federation when you opt in.

03Inspectable alwaysmind_stats shows nodes, sessions, and injection utility; the SQLite file opens in any browser.

Questions

Asked About the MCP Server.

How do I add memory to Claude Code?

Point Claude Code at Anvaya's mind-mcp server: five lines of .mcp.json in your project root. Claude Code then gets 8 memory tools — query, search, record, stats, sessions, threads — backed by your local graph. No account, no hosted service, memory stays under .anvaya/mind/.

Does it work with Cursor, Codex, or other MCP clients?

Yes — any MCP-compatible client speaks the same protocol. Anvaya CLI uses faster native transports (Direct <0.5ms, IPC ~2ms); MCP (~10ms) is the universal bridge for third-party harnesses.

What does a budgeted query mean?

mind_query takes a token_budget (default 4096) and the server packs the best context that fits: top critical nodes first, then patterns, fixes, concepts. Your agent gets high-signal memory at a fixed, predictable cost per call.

Is my code sent anywhere?

No. The MCP server is your local daemon over stdio/Unix socket. Queries never leave your machine unless you independently configure a cloud LLM provider for the agent itself.

Stop Starting From Zero.

One binary. 11+9 Rust crates. 545 tests. Hand-written HNSW index. Three transport modes. Four providers, Ollama, Anthropic, OpenAI, Siemens. Zero API keys required to start. Mind remembers everything after the first session.

Get Started →Read the FAQ