EchoVault Memory
Give coding agents durable local memory for decisions, bugs, and session context so you stop re-explaining the same project story every chat.
Overview
EchoVault is an MCP server for the Operate phase that provides local-first memory so coding agents retain decisions, bugs, and context across sessions.
What is this MCP server?
- Local-first memory store for coding agents across sessions
- Persists decisions, bugs, and contextual notes on disk
- OCI package ghcr.io/go-ports/echovault:0.3.3 with MEMORY_HOME mount (default /app/.memory)
- stdio transport for MCP clients without a cloud memory vendor
- Server version 0.3.3 (OCI ghcr.io/go-ports/echovault)
- Default memory directory MEMORY_HOME=/app/.memory
Community signal: 4 GitHub stars.
What problem does it solve?
Agent chats forget prior decisions and bug hunts, forcing you to repeat context and re-debug the same issues.
Who is it for?
Solo builders running Claude Code or Cursor daily on one codebase who want private, local session memory without Notion copy-paste.
Skip if: Teams needing shared collaborative knowledge bases, fine-grained ACLs, or cloud-synced docs as the system of record.
What do I get? / Deliverables
Decisions and debugging context persist in MEMORY_HOME so your agent can recall and update project memory on the next session.
- On-disk memory store readable and writable by the agent via MCP
- Cross-session recall of decisions, bugs, and project context
- Configurable memory root via MEMORY_HOME for backups and portability
Recommended MCP Servers
Journey fit
Long-running solo products depend on remembering past fixes and choices; Operate covers sustaining velocity across many agent sessions. Iterate is where context carryover prevents rework—EchoVault is shelved here as persistent memory for ongoing development loops.
How it compares
Local MCP memory layer for agents, not a project-management kanban or a vector RAG stack.
Common Questions / FAQ
Who is EchoVault for?
Indie developers and agent-first workflows that need persistent, local context across many coding sessions without sending memory to a SaaS.
When should I use EchoVault?
Use it during Operate and iterate loops when you want the agent to remember past decisions, bugs, and notes instead of starting from zero each time.
How do I add EchoVault to my agent?
Run ghcr.io/go-ports/echovault:0.3.3 with MEMORY_HOME mounted to persistent storage, register the stdio MCP server in your client, and ensure the memory directory survives restarts.