EchoVault Memory runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 18 Aug 2026.
Local-first memory for coding agents; stores decisions, bugs, and context across sessions.
What the code does
We read the source, 23 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
return filepath.Join(cwd, dotDir)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to EchoVault Memory
same job, measured the same wayDeterministic context selection for AI coding agents. Local memory that compounds across sessions.
Local-first, cross-harness memory for AI coding agents.
Memory for coding agents: the decisions, the dead ends, and where the last session stopped.
Task queue, decisions and memory for coding agents. Local SQLite, no network. Requires Bun.
Local-first memory and session continuity for AI coding agents over MCP. No cloud, no telemetry.
Local-first AI context and memory server for cross-tool coding continuity.
Session memory for AI coding agents: records decisions and dead ends, flags what went stale.
Session memory for coding agents: local-first recall, drift detection, on-device inference.
EchoVault Memory — questions
Answers built from our own checks of this server.