Integrations

Use Claude Recall with the editors and agents you already run.

Claude Recall ships as a single npm package with four surfaces: a CLI, a local web UI, a terminal interactive view, and an MCP server. The MCP server is the universal integration: any MCP-aware editor can read your session history through it. The terminal-native CLI works alongside any editor, including the ones that have not shipped MCP support yet.

Two different kinds of thing are listed below. Most of these make another editor a client of your history: install the extension or add the MCP server, and that editor can read sessions Claude Recall has already indexed. Codex is the other kind. It is a source: Claude Recall indexes OpenAI Codex CLI sessions itself, on by default, with nothing to configure, and they sit in the same lists and the same search as your Claude Code sessions.

VS Code

Native extension

Install from the Marketplace. Inline session browsing, search, and context re-injection without leaving the editor.

Codex

Indexed source

Nothing to configure. Codex CLI sessions are indexed on by default, badged, searchable next to your Claude Code sessions, and priced at OpenAI list rates.

Cursor

MCP server

One block in Cursor settings exposes every Claude Recall tool to Cursor Composer. Local. Stdio transport.

Claude Desktop

MCP server

Add the recall MCP server to claude_desktop_config.json. Claude Desktop can now search every Claude Code session you have ever run.

Windsurf

MCP server

Wire Claude Recall as an MCP server inside Windsurf so Cascade can recall context from your Claude Code history.

Zed

MCP server + terminal

Zed is MCP-native. Drop the recall server into your Zed config and use the agent panel against your local index.

Neovim

Terminal-native

Neovim users live in the terminal. recall, recall tui, and recall open work natively next to your editor.

Whichever of these you use, the install starts the same way.

Install Claude Recall →·MCP server overview

Last updated September 2026