claude-historian

claude-historian-mcp is an MCP server that lets Claude browse and search your Claude Code conversation history. It provides fast search across past solutions, tracks changes to files, and surfaces contextual history that can inform current work. Core tools exposed by the MCP include search_conversations to quickly locate past discussions and solutions, find_file_context to track edits and notes on specific files, get_error_solutions to retrieve fixes for recurring errors, find_similar_queries to surface related questions you've asked before, and list_recent_sessions to audit recent Claude sessions. Run the MCP locally with npx claude-historian-mcp, then configure your MCP to point to the server name you choose (for example claude-historian-mcp) so Claude can invoke these tools during your workflows.

Prerequisites:

• Node.js v20 or newer (npx is included with Node.js).
• Access to the Claude MCP environment where you will register this server.

Installation steps:

1. Ensure Node.js is installed (v20+):

   • macOS/Linux: curl -fsSL https://deb.nodesource.com/setup_20.x | bash - sudo apt-get install -y nodejs
   • Windows: install Node.js from https://nodejs.org/

2. No npm install is required for this MCP server. You can run it directly with npx:

   • From shell: claude mcp add claude-historian-mcp -- npx claude-historian-mcp

3. If npx resolves the wrong package, force resolution:

   • npm install -g claude-historian-mcp

4. Alternative MCP config (manual mcp.json): { "mcpServers": { "claude-historian-mcp": { "command": "npx", "args": ["claude-historian-mcp"], "env": {} } } }

5. Verify installation by invoking the MCP via your Claude integration and confirming the server name claude-historian-mcp is reachable.

Notes:

• This project was renamed from claude-historian to claude-historian-mcp. Update any existing MCP configs to use claude-historian-mcp and the new command if you were previously using claude-historian.
• There are no external databases or npm install steps required; the MCP relies on built-in search algorithms.
• If you encounter resolution issues with npx, you can install globally via npm install -g claude-historian-mcp and reference it directly in your MCP configuration.
• You can still leverage the optional Claude skill and the Claude Emporium plugin to enhance proactive history usage, but they are separate from the MCP server itself.
• Environment variables are supported in the mcp config (env block). Currently, this setup uses an empty env block by default.