Windsurf

Overview

Windsurf supports MCP servers natively through Cascade's settings. Once Rekall is registered, its 40+ memory tools become available to Cascade — creating memories, semantic search, entities, workflows, execution state, and more.

Prerequisites

• check_circleWindsurf installed (the Cascade agent supports MCP)
• check_circleA local Rekall checkout with the start-mcp.sh launch script
• check_circleNode.js 18+ (the script runs the MCP server with npx tsx)

Step 1: Locate the Config File

Windsurf reads MCP servers from mcp_config.json. Open it from the Cascade panel (the hammer / MCP icon → Configure → View raw config), or edit it directly:

~/.codeium/windsurf/mcp_config.json

Step 2: Add the Rekall Server

Add a rekall entry under mcpServers. The launch command runs Rekall's start-mcp.sh script via bash — use the absolute path to the script in your checkout:

{
  "mcpServers": {
    "rekall": {
      "command": "/bin/bash",
      "args": [
        "/absolute/path/to/rekall/start-mcp.sh"
      ],
      "env": {
        "REKALL_USER_ID": "your_user_id",
        "WORKSPACE": "work"
      }
    }
  }
}

Step 3: Verify the Connection

Open the Cascade MCP panel and confirm rekall shows a connected indicator with its tools listed. You can also ask Cascade directly:

You: "Do you have access to Rekall memory tools?"

Cascade: "Yes — the rekall MCP server is connected. I can create and search
memories, manage entities and workflows, and read agent context."

Using Memory in Windsurf

Ask Cascade to remember decisions as it works, and it will recall them on future sessions in the same workspace:

You: "Remember that this repo uses pnpm, not npm, and all tests run with vitest."

Cascade: [stores a semantic memory] "Noted — I'll use pnpm and vitest going forward."

--- later, new session ---

You: "Add a test for the new parser."

Cascade: [recalls memory] "I'll add a vitest test and run it with pnpm, matching
this repo's conventions."

Troubleshooting