Claude Recall in Windsurf
Windsurf Cascade is MCP-aware. Add Claude Recall as a server and Cascade gains access to every past Claude Code session you have ever run. Pure stdio. No HTTP. No remote calls.
Setup
Two commands plus one Windsurf setting.
# 1. Install the CLI
npm install -g @clauderecallhq/cli
# 2. In Windsurf: Settings → Cascade → MCP servers → Add server
# Name: recall
# Command: claude-recall-mcpOr edit the Windsurf MCP config file directly:
{
"mcpServers": {
"recall": {
"command": "claude-recall-mcp"
}
}
}What Cascade can do with it
- Search every past Claude Code session in the corpus.
- Pull any past session into the current Cascade chat as context.
- Find semantically similar sessions to whatever you are working on now.
- Browse tags, projects, and recent activity from the agent panel.
FAQ
Does Claude Recall capture Windsurf Cascade sessions?
No. Claude Recall reads ~/.claude/projects/ JSONL files written by Anthropic Claude Code, and OpenAI Codex CLI sessions at ~/.codex/. Windsurf Cascade has its own log format that lives elsewhere and is not indexed.
Will Cascade automatically pull context from my past Claude Code sessions?
Cascade can call the recall MCP tools when it judges they are relevant. To force it, ask explicitly: "Search my Claude Code sessions for X" or "Pull context from session abc12345".
Is this a Windsurf-fork-compatible workflow?
Yes, and both halves are available. Windsurf is a VS Code fork, and the Claude Recall extension supports it directly: Windsurf is one of the four editor targets the installer knows about, alongside VS Code, VS Code Insiders and Cursor, and it gets the same terminal auto-naming and status bar as the others. Install it from Open VSX, or point the Windsurf CLI at the .vsix with `windsurf --install-extension <file>.vsix`. The MCP integration described on this page is the complementary half: the extension names your terminals, MCP gives Cascade your session history. Either one works on its own.
Last updated September 2026