Skip to content

MCP server

New in v0.5. Expose Recall to Claude Desktop, Claude Code, or any other Model Context Protocol client so the model can search and pull in your past sessions natively — no copy-paste required.

What it exposes

Six read-only tools (the server never writes):

| Tool | What it does | |---|---| | list_projects | Every indexed project with session + message counts | | list_sessions | Recent sessions, optionally filtered by project / tag / date | | list_tags | Every tag currently in use with counts | | search | Full-text search; supports #tag-name tokens inline | | get_session | Full transcript for a session (accepts 8+-char id prefix) | | context_for_session | The moat: condensed or full markdown ready to paste as context |

Claude Code

Add to ~/.claude.json (or the equivalent per-project .mcp.json):

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

If you installed via npm link, the claude-recall-mcp binary is on your PATH. Otherwise point command at the built entry: node + args: ["/abs/path/to/dist/mcp/server.js"].

Claude Desktop

Add the same block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the Windows equivalent, then restart Claude Desktop.

Try it

Once wired in, ask the model:

  • "Search my past sessions for Hono server setup and show me what we decided."
  • "Pull in the context from session abc12345 and continue from there."
  • "What tags do I have?"

Local-only, always

The MCP server speaks stdio only — no network ports, no outbound calls. The same SQLite file and the same condensed-context formatter power it, so whatever the web UI shows, the MCP client sees.