Recallbase / Cursor + Recallbase

Give Cursor a persistent memory

Cursor is a strong AI editor – with Recallbase over MCP it gains a memory that keeps project history and decisions across sessions.

Why Cursor needs a memory

Cursor knows your code, but not the story of your decisions. Recallbase adds persistent project memory via the MCP server Cursor supports.

Set up Recallbase in Cursor

Prerequisite: a Recallbase account (create one free) and the installed client. Add the MCP server to Cursor's MCP configuration (e.g. ~/.cursor/mcp.json or .cursor/mcp.json in the project):

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

After restarting Cursor, 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 Cursor

Put the MCP configuration in .cursor/mcp.json so the team shares the same memory. In Cursor rules you can anchor memory_context at session start.

Read more: Codex CLI OpenCode Claude Code