Claude Recall in Zed
Zed is MCP-native through its context servers feature. Register Claude Recall as a context server and the Zed agent panel can search, recall, and inject any past Claude Code session as conversation context. Local. No HTTP. No API keys.
Setup
Edit settings.json. Restart Zed. The agent panel sees the recall server.
# Install the CLI
npm install -g @clauderecallhq/cliThen in Zed settings.json:
{
"context_servers": {
"recall": {
"command": {
"path": "claude-recall-mcp",
"args": [],
"env": {}
}
}
}
}What the Zed agent gains
- list_projects, list_sessions, list_tags: corpus navigation tools.
- search: full-text search across every past Claude Code session.
- find_similar_sessions (Pro): semantic similarity over local embeddings.
- get_session: fetch a full session transcript by id.
- apply_tags, set_alias, add_note: write features that respect the three-layer durability invariant.
FAQ
Does Claude Recall index Zed agent panel sessions?
No. Claude Recall is purpose-built for Anthropic Claude Code session JSONLs at ~/.claude/projects/. Zed agent conversations are stored separately by Zed and are not part of the Claude Recall corpus.
Why is the Zed config different from Cursor or Claude Desktop?
Zed exposes MCP servers under the context_servers key with a structured command object (path, args, env), while Claude Desktop and Cursor use the more common mcpServers shape with a single command string. Same protocol, different config schema.
Does it work with Zed on Linux?
Yes. Claude Recall ships native binaries for macOS (Apple Silicon and Intel), Linux x64 / arm64 (glibc), and Windows 10+ x64. Zed runs on all three.
Last updated April 2026