Claude Desktop

Connect Rekall to Claude Desktop so your conversations gain persistent memory. Claude will remember past interactions, user preferences, and project context across sessions.

Prerequisites

  • check_circleClaude Desktop installed and running (version 1.0 or later)
  • check_circleNode.js 18+ installed on your machine
  • check_circleA Rekall API key from your dashboard settings

Step 1: Install the MCP Server

Install the Rekall MCP server globally using npm:

Terminal
npm install -g @rekall/mcp-server

This makes the rekall-mcp command available system-wide.

Step 2: Locate the Config File

Claude Desktop reads MCP server configuration from a JSON file. The location depends on your operating system:

Config file location
~/Library/Application Support/Claude/claude_desktop_config.json

File may not exist yet

If you have never configured an MCP server before, the file may not exist. Create it with an empty JSON object {} and add the configuration in the next step.

Step 3: Add the Rekall Server Entry

Open the config file in your text editor and add the Rekall MCP server entry under mcpServers:

claude_desktop_config.json
{
  "mcpServers": {
    "rekall": {
      "command": "rekall-mcp",
      "args": ["--stdio"],
      "env": {
        "REKALL_API_KEY": "your-api-key-here"
      }
    }
  }
}

Replace the API key

Replace your-api-key-here with your actual Rekall API key. You can generate one from the dashboard settings. Never share your API key or commit it to version control.

If you already have other MCP servers configured, add the "rekall" entry alongside them:

claude_desktop_config.json (multiple servers)
{
  "mcpServers": {
    "existing-server": {
      "command": "existing-command",
      "args": ["--stdio"]
    },
    "rekall": {
      "command": "rekall-mcp",
      "args": ["--stdio"],
      "env": {
        "REKALL_API_KEY": "your-api-key-here"
      }
    }
  }
}

Step 4: Restart Claude Desktop

After saving the configuration file, fully quit and restart Claude Desktop. The application reads the MCP config on startup, so a restart is required for changes to take effect.

desktop_mac

macOS

Cmd+Q to quit, then reopen from Applications or Spotlight.

desktop_windows

Windows

Right-click the system tray icon and select Quit, then reopen.

computer

Linux

Close the window and end the process, then relaunch.

Step 5: Verify the Connection

After restarting, look for the MCP tools icon (a hammer icon) in the Claude Desktop input area. Click it to see a list of available tools -- you should see Rekall's 40+ memory tools listed.

You can also verify by asking Claude directly:

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


Claude: "Yes! I can see the Rekall MCP server is connected. I have
access to tools for creating memories, searching, managing entities,
workflows, execution state, and more. Would you like me to create
a memory or search for something?"

Check the tools list

If you see tools like create_memory, search_memories, and get_agent_context in the tools menu, the connection is working correctly.

Example Conversations

Here are examples of how Claude uses Rekall memory in conversations:

Storing a decision

You:"We decided to use PostgreSQL instead of MongoDB for the user service. The main reasons were ACID compliance and our team's existing expertise."
Claude:"I've stored that decision as an episodic memory. I'll remember that your team chose PostgreSQL for the user service, with ACID compliance and team expertise as the key factors."

Recalling past context

You:"What database did we pick for the user service?"
Claude:"You chose PostgreSQL for the user service. The decision was made because of ACID compliance requirements and your team's existing PostgreSQL expertise."

Learning preferences

You:"Can you give me shorter responses? I prefer concise answers without lengthy preambles."
Claude:"Noted -- I've saved your preference for concise responses. I'll keep future answers brief and to the point."

Troubleshooting

Tools not appearing

Make sure you fully quit Claude Desktop (not just closed the window) and relaunched it. Check that the config file path is correct for your OS and that the JSON is valid.

Authentication errors

Verify your REKALL_API_KEY is correct. Generate a new key from the dashboard if needed. Ensure there are no extra spaces or newlines in the key value.

Command not found

If rekall-mcp is not found, ensure the npm global bin directory is in your PATH. Run npm bin -g to find the directory and add it to your shell profile.

Rekall
rekall