Cline

Overview

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

Prerequisites

• check_circleVS Code with the Cline extension installed
• 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

Cline stores MCP server settings in cline_mcp_settings.json. You can open it from the Cline panel (the MCP Servers icon → Configure MCP Servers), or edit it directly:

~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.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

Save the file. Cline reloads MCP settings automatically; open the MCP Servers panel and confirm rekall shows a green connected indicator with its tools listed. You can also ask Cline directly:

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

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

Using Memory in Cline

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

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

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

--- later, new task ---

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

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

Troubleshooting