OpenCode integrates with EchoVault via MCP. One command installs the MCP server entry, and OpenCode automatically uses memory tools during sessions.
Installation
Install EchoVault
pip install git+https://github.com/mraza007/echovault.git
memory init
Run setup
This writes the MCP server config to ~/.config/opencode/opencode.json. Restart OpenCode
Restart OpenCode to load the new MCP server.
What gets installed
The setup command adds an mcp entry to ~/.config/opencode/opencode.json:
{
"mcp": {
"echovault": {
"type": "local",
"command": ["memory", "mcp"]
}
}
}
memory mcp at session start and gains access to three tools:
memory_savememory_searchmemory_context
OpenCode uses a different MCP config schema than Claude Code and Cursor. The setup command handles this automatically.
Project-scoped installation
To install memory for a specific project instead of globally:
cd ~/my-project
memory setup opencode --project
opencode.json in the project root instead of ~/.config/opencode/opencode.json. OpenCode loads project-local config when available.
memory setup opencode
# Writes to: ~/.config/opencode/opencode.json
Config file locations
| Scope | Config file | Used when |
|---|
| Global | ~/.config/opencode/opencode.json | No project-local config exists |
| Project | opencode.json | Present in project root |
If both files exist, OpenCode prioritizes the project-local opencode.json.
Uninstalling
To remove EchoVault from OpenCode:
memory uninstall opencode
echovault entry from ~/.config/opencode/opencode.json. For project-scoped installs:
memory uninstall opencode --project
opencode.json.
Your memory vault at ~/.memory/vault/ is not deleted. Only the MCP config is removed.
Usage
Once installed, OpenCode automatically:
- Calls
memory_context --project at session start to load recent memories
- Calls
memory_search <query> when searching for relevant context
- Calls
memory_save to persist decisions, bugs, and learnings
You don’t need to prompt OpenCode to use memory. The MCP tool descriptions instruct it to save and retrieve automatically.
Use memory config to verify your setup and check the effective memory home path.
OpenCode MCP schema
OpenCode uses a different MCP config format than other agents:
{
"mcp": {
"echovault": {
"type": "local",
"command": ["memory", "mcp"]
}
}
}
{
"mcpServers": {
"echovault": {
"command": "memory",
"args": ["mcp"],
"type": "stdio"
}
}
}