Which clients work?
Any MCP-compatible client: Claude Code, Cursor, Codex CLI, Windsurf, Gemini CLI, OpenCode. The protocol is identical; only the config location differs per client.
Docs · MCP Setup (Claude Code, Cursor, …)
One memory, every harness.
Direct answer
Anvaya's MCP server exposes your local graph to any MCP client over stdio: 14 tools, budgeted queries (default 4096 tokens), zero accounts. Five lines of .mcp.json in your project root, restart the client, and Claude Code, Cursor, or Codex CLI reads and writes the same memory Anvaya CLI uses natively.
MCP Setup (Claude Code, Cursor, …)
Questions
Any MCP-compatible client: Claude Code, Cursor, Codex CLI, Windsurf, Gemini CLI, OpenCode. The protocol is identical; only the config location differs per client.
MCP ~10ms per call vs Direct <0.5ms / IPC ~2ms inside Anvaya CLI. Irrelevant next to model latency; the bridge tax is noise.
No, stdio to your local daemon. Cloud exposure depends only on which LLM provider your agent itself uses.
25.6 MB median RSS. 25 agents ran in parallel on a Core 2 Duo with 4 GB RAM. Hundreds on your machine. Zero cloud required on the Ollama path.
Requires Rust/cargo to build from source. Linux and macOS today, Windows not yet supported. Pre-1.0, public beta. Pricing TBD.