The Ecosystem · TWO BINARIES, ONE GRAPH
Two Tools.One Memory.
The CLI is an agent that executes. Mind is a daemon that remembers — and over MCP it becomes a memory server for Claude Code and any MCP client. They’re separate binaries from separate repos on purpose: run either one without the other, and Mind will happily serve a client that isn’t Anvaya at all.
The Split
Why Two Binaries.
11 crates · ~40K lines of Rust · 7 TUI panels · 18 native tools · 4 providers · headless mode · ~12.1MB binary, zero runtime dependencies.
Learn more →9 crates · SQLite graph + Int8 HNSW index · 6 node types with per-type decay · 6 background workers · 8 MCP tools · 12-25x compression.
Learn more →The Bridge
Three Ways In, Same Graph.
Mind exposes the same memory through three transports. Which one you get depends on who is asking — and the cost difference between them is the difference between a function call and a protocol handshake.
MCP
Keep Your Agent. Add The Memory.
If you already work in Claude Code or another MCP client, you don’t have to adopt the CLI to get the memory. Point the client at mind-mcp and these eight tools appear inside the agent you already trust.
Setup is a five-line .mcp.json in your project root — see Get Started →
Stop Starting From Zero.
One binary. Four providers — Ollama, Anthropic, OpenAI, Siemens. Zero API keys required to start. Mind remembers everything after the first session.