Skip to content
Founder Pricing Ends May 31May 31
Integrations / Cursor

Claude Recall in Cursor

Cursor is MCP-native as of late 2024. Add Claude Recall as a server and Cursor Composer can search, recall, and inject any past Claude Code session as context. The recall server speaks stdio only, runs on your machine, and authenticates nothing because there is nothing remote to authenticate against.

Setup

Two terminal commands plus one Cursor setting.

# 1. Install the CLI
npm install -g @clauderecallhq/cli

# 2. Open Cursor → Settings → Features → MCP → Add new MCP server
#    Name: recall
#    Command: claude-recall-mcp

Or edit the MCP config file directly:

{
  "mcpServers": {
    "recall": {
      "command": "claude-recall-mcp"
    }
  }
}

What Cursor can do with it

Why this works without any account

MCP runs over stdio between two processes on the same machine. Cursor spawns the recall MCP server as a child process; they speak via stdin/stdout. There is no network hop, no credential exchange, and no third-party server in between. The recall server only reads the local SQLite index at ~/.recall/ that Claude Recall maintains by watching ~/.claude/projects/.

FAQ

Does Claude Recall index Cursor sessions?

No. Claude Recall is purpose-built for Claude Code session JSONLs at ~/.claude/projects/. The Cursor integration lets Cursor read your Claude Code session memory; it does not capture Cursor's own conversation log.

Do I need an API key for the Cursor integration?

No. The MCP server speaks stdio to Cursor. There is no HTTP, no auth token, no API key. The server reads only the local SQLite index that Claude Recall maintains.

What MCP tools does Cursor get access to?

list_projects, list_sessions, list_tags, search, find_similar_sessions (Pro), apply_tags, set_alias, add_note, get_session, and more. Full tool list is on the MCP page at https://clauderecall.com/mcp.

Last updated April 2026