Continue

Overview

Continue supports MCP servers as blocks in its YAML configuration. Once Rekall is registered, its 40+ memory tools become available to Continue's agent — creating memories, semantic search, entities, workflows, execution state, and more.

Prerequisites

• check_circleThe Continue extension installed in VS Code or JetBrains
• 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

Continue defines MCP servers in a YAML config block. You can add one as a local workspace block in .continue/mcpServers/, or in your global config:

.continue/mcpServers/rekall.yaml

Step 2: Add the Rekall Server

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

name: Rekall MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: rekall
    command: /bin/bash
    args:
      - /absolute/path/to/rekall/start-mcp.sh
    env:
      REKALL_USER_ID: your_user_id
      WORKSPACE: work

Continue's agent mode is where MCP tools are surfaced — switch the chat to Agent mode to let it call Rekall's tools.

Step 3: Verify the Connection

Save the file. Continue reloads MCP blocks automatically; open the tools menu in Agent mode and confirm rekall's tools are listed. You can also ask the agent directly:

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

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

Using Memory in Continue

In Agent mode, ask Continue 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."

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

--- later, new session ---

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

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

Troubleshooting