Q
Which memory MCP should I pick?
By question shape: human-readable notes (markdown servers), resumable multi-step work (issue-graph), semantic recall over big corpora (vector+graph). Anvaya covers the code-native corner.
Glossary · MCP Memory Server
MCP Memory Server.
One memory, every harness.
Direct answer
A Model Context Protocol server exposing memory as tools (query, search, record, stats, sessions) so any MCP client — Claude Code, Cursor, Codex, Windsurf — reads and writes one shared store. The install pattern is identical stdio JSON everywhere; the memory model is the real choice (markdown notes vs issue graph vs vector+graph). Local-first servers keep proprietary code on disk; hosted ones trade sovereignty for zero ops.
In Anvaya
How We Implement It.
01MCP Memory Servermind-mcp serves 8 tools with budgeted queries (default 4096 tokens); Anvaya CLI itself uses faster native transports (Direct <0.5ms, IPC ~2ms).
Questions
Asked About MCP Memory Server.
Q
Can two different agents share one memory?
Yes — that's the point. Record a fix in the terminal, recall it in the IDE; per-agent scoping available where needed.
Q
Local or hosted memory server?
Local for proprietary code and offline; hosted for zero-ops teams. Never send contract-covered code to a SaaS to save a setup afternoon.
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.