Skip to content
MCP server
Stdio MCP server. Same SQLite, no network ports.
Claude Desktopclaude_desktop_config.jsonClaude Code~/.claude.jsonstdioclaude-recall-mcpno ports · no outbounddb.sqlite~/.recall/Whatever the web UI shows, the MCP client sees the same.
📖
Read tools
always on
  • list_projectsevery project + counts
  • list_sessionsrecent, filterable
  • searchBM25 + RRF fusion
  • find_similar_sessionscosine semantic (Pro)
  • get_sessionfull transcript
  • context_for_sessioncondensed markdown
  • recall_neighborhoodparents/children/citations
  • locate_sessionsfind an old session (Pro)
  • bucket_list / bucket_searchyour own docs
  • thread_list / thread_getthread browsing
  • list_tagsevery tag + counts
  • doctorlocal health snapshot
✏️
Write tools
--allow-writes
  • add_tag / remove_tagtag management
  • set_aliasarchive prior values
  • append_noteadd markdown to a note
  • create_collectionplus add/remove session
  • thread_createplus link, set-parent, remove
  • thread_rename / archivelifecycle
  • thread_merge / splitrestructuring
  • sync_active_sessionscapture running terminals
  • apply_tagsmerge-mode tagging
Writes are rate-limited (default 60/min, shared across all write tools), zod-validated, and recorded in the mcp_audit_events table in ~/.recall/db.sqlite.

MCP server

One stdio server, serving the same SQLite the web UI reads. Setup:

#Claude Code

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

In ~/.claude.json (or per-project .mcp.json). If you installed via npm link, claude-recall-mcp is on your PATH; otherwise point command at node with args: ["/abs/path/to/dist/mcp-server.js"].

#Claude Desktop

Same block in ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the Windows equivalent. Restart the app.

#Codex

Codex keeps its MCP servers in its own config.toml, inside the Codex home. Recall does not write Codex config files and does not read that one, so this step is a hand-off: run the command and Codex writes its own config.

bash
codex mcp add recall -- claude-recall-mcp

codex mcp list shows the result and codex mcp remove recall undoes it. Running the add again is safe; it leaves every other setting alone. To paste rather than run, the same entry is:

toml
[mcp_servers.recall]
command = "claude-recall-mcp"

If claude-recall-mcp is not on your PATH, put node in the command position and the absolute path to dist/mcp-server.js after it, in either form.

#Both agents are served

The MCP server answers out of one index covering both agents, so a Codex question can be answered from a Claude Code session and the other way round. get_session and context_for_session name the agent that wrote the session, and list_sessions, search and find_similar_sessions take a source parameter of all (the default), claude or codex to narrow to one.

#Try it

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

stdio transport. No ports. Whatever the web UI shows, the MCP client sees the same SQLite.

Last updated