Crixin runs as an MCP server so the host can search your sessions as a tool. Install takes one minute. The package is on npm — no clone, no build.
Requires Node ≥ 22. nodejs.org if you don't have it.
One click. Cursor opens a confirmation dialog and writes the entry into its MCP config.
Add to Cursor Copy manual JSON instead
{
"mcpServers": {
"crixin": {
"command": "npx",
"args": ["-y", "crixin", "--mcp"]
}
}
}
list_recent_sessions and reply with newest sessions across all three sources.
One command. The CLI handles the config file edit; restart Claude Code afterwards.
claude mcp add crixin -- npx -y crixin --mcp
~/.claude/mcp.json by hand{
"mcpServers": {
"crixin": {
"command": "npx",
"args": ["-y", "crixin", "--mcp"]
}
}
}
search_sessions and reply with snippets + ready-to-paste claude --resume <uuid> commands.
Append the block below to ~/.codex/config.toml. Codex picks up MCP servers on every launch.
[mcp_servers.crixin] command = "npx" args = ["-y", "crixin", "--mcp"]
stats tool and reply with totals (sessions, messages, est. spend, busiest hour).
If you're not running an MCP-aware host yet, you can still use the dashboard standalone:
npx -y crixin
http://127.0.0.1:<random-port>. First run on a 17k-message history takes ~80s for the BPE-tokenized cost estimate; subsequent runs are sub-second thanks to the mtime cache.
You ran crixin directly without installing globally. Either npx -y crixin … (one-shot) or npm i -g crixin (then plain crixin).
Crixin uses Node's built-in node:sqlite module which lands at Node 22. Upgrade with nvm install 22 or brew install node.
You added the entry but the running session uses its cached MCP list. Quit Claude Code completely (the menu-bar icon, not just the window) and reopen.
Make sure Cursor is your default cursor:// handler. On macOS, run Cursor once with the deep-link manually pasted into Safari's address bar — the OS will register the handler.
That's the BPE cost-estimation pass on your full session history. Subsequent runs use the cache at ~/.crixin/crixin.db and start in <1s.
The npm registry is occasionally unreachable from China / Egypt. Use npm i -g crixin --registry https://registry.npmmirror.com as a fallback.
A few prompts that exercise the four tools we expose. Run them in your AI coding host of choice.
list_recent_sessions
search_sessions with a snippet + resume command per hit
get_session and returns the full transcript as Markdown
stats with sessions, messages, est. spend, busiest hour, top projects
The MCP server above is the same binary as the dashboard. Run npx -y crixin in any terminal to open the browser dashboard whenever you want a visual view of the same data.