
Claude Historian
STDIOMCP server for searching Claude Code conversation history with smart prioritization algorithms
MCP server for searching Claude Code conversation history with smart prioritization algorithms
A Model Context Protocol (MCP) server for searching your Claude Code (& Claude Desktop) conversation history. Find past solutions, track file changes, and learn from previous work.
Requirements:
npm install -g claude-historian
From shell:
claude mcp add claude-historian -- npx claude-historian
From inside Claude (restart required):
Add this to our global mcp config: npx claude-historian
Install this mcp: https://github.com/Vvkmnn/claude-historian
From any manually configurable mcp.json
: (Cursor, Windsurf, etc.)
{ "mcpServers": { "claude-historian": { "command": "npx", "args": ["claude-historian"], "env": {} } } }
That's it; there is no npm install
required as there are no external dependencies or local databases, only search algorithms.
However, in the unlikely event that you pull the wrong package / npx
registry is out of date, you can force resolution issues in certain environments with:
npm install -g claude-historian
MCP server that gives Claude access to your conversation history. Fast search with smart prioritization.
Runs locally (with cool shades [⌐■_■]
):
[⌐■_■] search_conversations query=<query>
> "How did we fix that Redis connection pooling nightmare?"
> "Docker container keeps crashing on Kubernetes deployment"
> "React infinite re-render loop - useEffect dependency hell"
[⌐□_□] find_file_context filepath=<filepath>
> "package.json changes that broke everything last month"
> "When we accidentally committed .env to main branch"
> "Authentication service refactor - before/after comparison"
[⌐×_×] get_error_solutions error_pattern=<error>
> "MODULE_NOT_FOUND - the classic npm/yarn version mismatch"
> "CORS preflight failing - but only on production Fridays?"
> "Database deadlock during Black Friday traffic spike"
[⌐◆_◆] find_similar_queries query=<query>
> "Database queries slower than my morning coffee brewing"
> "How to implement error boundaries without losing sanity"
> "State management: Redux vs Zustand vs just useState"
[⌐○_○] list_recent_sessions
> "Tuesday debugging marathon: 9pm-3am flaky test hunt"
> "Performance optimization sprint - reduced bundle 40%"
> "The great TypeScript migration of 2024"
[⌐⎚_⎚] find_tool_patterns tool_name=<tool>
> "Read → Edit → Bash combo for rapid prototyping"
> "When I use Grep vs Task for different searches"
> "Git operations during feature branch management"
How claude-historian works:
"docker auth" query
|
├─> Parallel Processing (search.ts:949): 15 projects × 10 files concurrently
| • Promise.allSettled for 6x speed improvement
| • Early termination when sufficient results found
| • Enhanced file coverage with comprehensive patterns
|
├─> Enhanced Classification (search.ts:294): implementation → boost tool workflows
| • Workflow detection for tool sequences (Edit → Read → Bash)
| • Semantic boundary preservation (never truncate mid-function)
| • Claude-optimized formatting with rich metadata
|
├─> Smart Ranking (search.ts:213):
| • "Edit workflow (7x successful)" (2h ago) *****
| • "Docker auth with context paths" (yesterday) ****
| • "Container debugging patterns" (last week) ***
|
└─> Return Claude Code optimized results
Core optimizations:
Promise.allSettled
for 6x speed improvement across projects and filesSearch strategies:
File access:
~/.claude/conversations/
git clone https://github.com/vvkmnn/claude-historian && cd claude-historian npm install && npm run build npm test
Package requirements:
@modelcontextprotocol/sdk
dependencyDevelopment workflow:
npm run build # TypeScript compilation with executable permissions npm run dev # Watch mode with tsc --watch npm run lint # ESLint code quality checks npm run format # Prettier formatting npm run type-check # TypeScript validation without emit npm run prepublishOnly # Pre-publish validation (build + lint + format)
Contributing:
Learn from examples:
Claude Desktop support is currently blocked by LevelDB locks and Electron sandboxing. You will still search Claude Desktop from Claude Code, but only when the Claude app is closed.
A DXT package and build is available for future compatibility; further investigations are ongoing. Feel free to test with it.
Claude Fauchet (1744-1793), French Historian