Recallbase / OpenCode + Recallbase

Give OpenCode a persistent memory

OpenCode plus Recallbase: a persistent, project-scoped memory over the MCP standard – shared across machines and team.

Why OpenCode needs a memory

OpenCode is open and flexible. Recallbase adds the missing recall: what was learned in one session is back in the next – across projects and team.

Set up Recallbase in OpenCode

Prerequisite: a Recallbase account (create one free) and the installed client. Add the MCP server to your project's opencode.json:

{ "mcp": { "recallbase": {
    "type": "local",
    "command": ["node", "/PATH/TO/.claude/brain-helper/dist/index.js", "mcp"] } } }

After restarting OpenCode, the MCP server recallbase is available.

The four memory tools

Over MCP, Recallbase gives your agent four tools:

• memory_context – loads the project memory into context
• memory_search – full-text and meaning search over past sessions
• memory_save_session – saves a structured summary
• memory_add_knowledge – writes durable knowledge into the graph

To have your agent use them automatically, add to its instruction file (e.g. AGENTS.md / GEMINI.md): "Call memory_context at the start of each session and apply the context. Save via memory_save_session at the end."

Tip for OpenCode

Since opencode.json lives per project, you can enable memory per project. The setup command adds it automatically when an opencode.json exists.

Read more: Gemini CLI Cursor Claude Code