Recallbase / Gemini CLI + Recallbase

Give Gemini CLI a persistent memory

Give the Gemini CLI a memory that persists across sessions: Recallbase connects over MCP and delivers project context on start.

A glowing ring of connected nodes – the Recallbase memory ring

Why Gemini CLI needs a memory

The Gemini CLI is versatile, but has no memory of earlier sittings. Recallbase adds exactly that – project memory over MCP, without changing your workflow.

All guides use the same MCP server. The fastest setup is the bundled command node ~/.claude/brain-helper/dist/index.js setup, which registers detected agents automatically. The manual entry is shown below as well.

Set up Recallbase in Gemini CLI

Prerequisite: a Recallbase account (create one free) and the installed client. Add the MCP server to ~/.gemini/settings.json:

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

After restarting Gemini CLI, the MCP server recallbase is available.

The four memory tools

Over MCP, Recallbase gives your agent four tools:

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 Gemini CLI

In GEMINI.md you can note that memory_context is used at the start and memory_save_session at the end – so the memory maintains itself.

Give your agent a memory

Start for free, no credit card. In two minutes your agent remembers every session.

Start for free