Vvkmnn/claude-historian-mcp

claude-historian-mcp

An Model Context Protocol (MCP) server for searching your Claude Code conversation history. Find past solutions, track file changes, and learn from previous work.

install

Requirements:

From shell:

claude mcp add claude-historian-mcp -- npx claude-historian-mcp

From inside Claude (restart required):

Add this to our global mcp config: npx claude-historian-mcp

Install this mcp: https://github.com/Vvkmnn/claude-historian-mcp

From any manually configurable mcp.json: (Cursor, Windsurf, etc.)

{
  "mcpServers": {
    "claude-historian-mcp": {
      "command": "npx",
      "args": ["claude-historian-mcp"],
      "env": {}
    }
  }
}

There is no npm install required -- no external dependencies or local databases, only search algorithms.

However, if npx resolves the wrong package, you can force resolution with:

npm install -g claude-historian-mcp

renamed: This project was renamed from claude-historian to claude-historian-mcp. Existing users should update your install command and MCP config args to claude-historian-mcp.

Optionally, install the skill to teach Claude when to proactively use historian:

npx skills add Vvkmnn/claude-historian-mcp --skill claude-historian --global
# Optional: add --yes to skip interactive prompt and install to all agents

This makes Claude automatically check your history before web searches, when encountering errors, or at session start. The MCP works without the skill, but the skill improves discoverability.

plugin

For automatic history search with hooks and commands, install from the claude-emporium marketplace:

/plugin marketplace add Vvkmnn/claude-emporium
/plugin install claude-historian@claude-emporium

The claude-historian plugin provides:

Hooks (targeted, zero overhead on success):

• Before WebSearch/WebFetch → Check find_similar_queries
• Before EnterPlanMode → Check search_plans
• Before Task agents → Check find_tool_patterns
• After Bash errors → Check get_error_solutions

Command: /historian-search <query>

Requires the MCP server installed first. See the emporium for other Claude Code plugins and MCPs.

features

MCP server that gives Claude access to your conversation history. Fast search with smart prioritization.

Runs locally (with cool shades [⌐■_■] 📜):

search_conversations

Search your conversation history for past solutions, discussions, and context.

[⌐■_■] 📜 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"

[⌐■_■] 📜 "docker auth" | 2 results

{
  "results": [{
    "type": "assistant",
    "ts": "2h ago",
    "content": "Fixed Docker auth by updating registry credentials...",
    "project": "my-app",
    "score": 15,
    "ctx": { "filesReferenced": ["docker-compose.yml"], "toolsUsed": ["Edit", "Bash"] }
  }]
}

find_file_context

Track modifications, edits, and discussions about specific files across sessions.

[⌐□_□] 📜 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"

[⌐□_□] 📜 "package.json" | 5 operations

{
  "filepath": "package.json",
  "operations": [{
    "type": "edit",
    "ts": "1d ago",
    "changes": ["added vitest dependency", "updated build script"],
    "ctx": { "filesReferenced": ["package.json", "vitest.config.ts"] }
  }]
}

get_error_solutions

Find how you've resolved similar errors before, with code fixes and patterns.

[⌐×_×] 📜 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"

[⌐×_×] 📜 "ENOENT no such file" | 2 solutions

{
  "solutions": [{
    "pattern": "ENOENT: no such file or directory",
    "frequency": 3,
    "fixes": [{ "content": "Created missing directory", "code": ["mkdir -p ./dist"] }]
  }]
}

find_similar_queries

Discover related questions you've asked before and their answers.

[⌐◆_◆] 📜 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"

[⌐◆_◆] 📜 "typescript error handling" | 3 similar

{
  "similar": [{
    "query": "how to handle async errors in typescript",
    "similarity": 0.72,
    "ts": "3d ago",
    "project": "api-server"
  }]
}

list_recent_sessions

Browse your recent Claude sessions with project context and accomplishments.

[⌐○_○] 📜 list_recent_sessions
  > "Tuesday debugging marathon: 9pm-3am flaky test hunt"
  > "Performance optimization sprint - reduced bundle 40%"
  > "The great TypeScript migration of 2024"

[⌐○_○] 📜 all | 3 sessions

{
  "sessions": [{
    "id": "68d5323b",
    "ts": "2h ago",
    "duration": 45,
    "messages": 128,
    "project": "my-app",
    "tools": ["Edit", "Bash", "Read"],
    "accomplishments": ["fixed auth bug", "added unit tests"]
  }]
}

find_tool_patterns

Learn from your successful tool usage workflows and common sequences.

[⌐⎚_⎚] 📜 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"

[⌐⎚_⎚] 📜 "Edit" | 3 patterns

{
  "tool": "Edit",
  "patterns": [{
    "name": "Read → Edit → Bash",
    "uses": 7,
    "workflow": "Read → Edit → Bash",
    "practice": "Read file, edit, then run tests (7x successful)"
  }]
}

search_plans

Search Claude Code plan files for past implementation approaches, decisions, and patterns.

[⌐▣_▣] 📜 search_plans query=<query>
  > "How did we architect the authentication system?"
  > "Database migration strategy from last refactor"
  > "API versioning approach we decided on"

[⌐▣_▣] 📜 "auth implementation" | 2 plans

{
  "plans": [{
    "file": "implement-oauth.md",
    "ts": "3d ago",
    "project": "my-app",
    "summary": "OAuth2 implementation with refresh tokens...",
    "decisions": ["chose PKCE flow", "JWT for access tokens"]
  }]
}

search_config

Search .claude configuration files (rules, skills, agents, CLAUDE.md) for guidance and patterns.

[⌐◈_◈] 📜 search_config query=<query>
  > "What are my rules about minimalism and code quality?"
  > "Find the systematic debugging skill documentation"
  > "Search for test-driven development guidelines"

[⌐◈_◈] 📜 "verify everything" | 2 results

{
  "results": [{
    "type": "assistant",
    "ts": "1/31/2026",
    "content": "# Verify Everything\n\n## Rule\nEvery claim must be anchored to evidence...",
    "file": "/Users/v/.claude/rules/verify.md",
    "category": "global-rules",
    "score": 34
  }]
}

search_tasks

Search task management data for pending, completed, and in-progress tasks.

[⌐◇_◇] 📜 search_tasks query=<query>
  > "Find pending tasks related to documentation"
  > "What tasks mention the authentication system?"
  > "Search for in-progress refactoring tasks"

[⌐◇_◇] 📜 "documentation" | 3 results

{
  "results": [{
    "type": "assistant",
    "ts": "4h ago",
    "content": "[PENDING] Update API documentation\nAdd missing endpoints and examples to the API docs",
    "file": "/Users/v/.claude/tasks/abc123/5.json",
    "score": 16
  }]
}

extract_compact_summary

Get a concise summary of what was accomplished in a specific session.

[⌐◉_◉] 📜 extract_compact_summary session_id=<id>
  > "What did we accomplish in last session?"
  > "Summarize the authentication refactor work"
  > "Key decisions from yesterday's debugging"

[⌐◉_◉] 📜 extracting summary from my-app (68d5323b)

{
  "session": {
    "id": "68d5323b",
    "ts": "2h ago",
    "duration": 45,
    "messages": 128,
    "project": "my-app",
    "tools": ["Edit", "Bash", "Read"],
    "files": ["src/auth.ts", "package.json"],
    "accomplishments": ["fixed auth bug", "added unit tests"],
    "decisions": ["chose JWT over sessions"]
  }
}

methodology

How claude-historian-mcp works:

"docker auth" query
      |
      ├─> Parallel Processing (search.ts:174): 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:642): 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 (utils.ts:267):
      |   ├─> Core Terms (scoring-constants.ts): "docker" +10, "auth" +10
      |   ├─> Supporting Terms: context words +3 each
      |   ├─> Tool Usage: Edit/Bash references +5
      |   ├─> File References: paths/extensions +3
      |   └─> Project Match: current project +5
      |
      ├─> Results sorted by composite score:
      |   • "Edit workflow (7x successful)" (2h ago) ***** [score: 45]
      |   • "Docker auth with context paths" (yesterday) **** [score: 38]
      |   • "Container debugging patterns" (last week) *** [score: 22]
      |
      └─> Return Claude Code optimized results

Core optimizations:

• parallel processing: Promise.allSettled for 6x speed improvement across projects and files
• workflow detection: Captures tool sequences like "Edit → Read → Bash" patterns
• enhanced file matching: Comprehensive path variations with case-insensitive matching
• intelligent deduplication: Content-based deduplication preserving highest-scoring results
• intelligent truncation: Never truncates mid-function or mid-error
• Claude-optimized formatting: Rich metadata with technical content prioritization

Search strategies:

• JSON streaming parser (parseJsonlFile): Reads Claude Code conversation files on-demand without full deserialization
• LRU caching (messageCache): In-memory cache with intelligent eviction for frequently accessed conversations
• TF-IDF inspired scoring (calculateRelevanceScore): Term frequency scoring with document frequency weighting for relevance
• Query classification (classifyQueryType): Naive Bayes-style classification (error/implementation/analysis/general) with adaptive limits
• Edit distance (calculateQuerySimilarity): Fuzzy matching for technical terms and typo tolerance
• Exponential time decay (getTimeRangeFilter): Recent messages weighted higher with configurable half-life
• Parallel file processing (getErrorSolutions): Concurrent project scanning with early termination for 0.8s response times
• Workflow pattern recognition (getToolPatterns): Detects tool usage sequences and related workflows for learning
• Enhanced file context (findFileContext): Multi-project search with comprehensive path matching
• Content-aware truncation (smartTruncation): Intelligent content boundaries over arbitrary character limits
• Technical content prioritization (BeautifulFormatter): Code blocks, errors, and file paths get full preservation
• Query similarity clustering (findSimilarQueries): Semantic expansion and pattern grouping for related questions

Design principles:

• Universal engine -- single search backend for all Claude Code conversations
• Parallel processing -- concurrent file scanning across session directories
• Semantic expansion -- query synonyms and related terms for better recall
• Zero dependencies -- only @modelcontextprotocol/sdk, no databases required
• Offline -- never leaves your machine, scans local JSONL files only

File access:

• Reads from: ~/.claude/conversations/
• Zero persistent storage or indexing
• Never leaves your machine

Performance: See for benchmarks, optimization history, and quality scores. Current (v1.0.5): 4.7/5 average score across 10 tools. ~0.9s per query, zero regressions.

alternatives

Every conversation history tool either loads context always (burning tokens when unused) or requires external runtimes and databases. Historian searches on-demand with zero dependencies.

Claude Memory -- Claude's built-in memory (CLAUDE.md + auto-memory). Persists project rules and preferences across sessions. Forward-looking ("always use ESM imports"); not conversation search. Complementary: memory for rules, historian for past solutions.

claude-mem -- Plugin that captures observations via lifecycle hooks, compresses them into SQLite + Chroma, and loads context every session. Requires Bun, Python, and a background worker on port 37777. Real-world testing (270+ sessions): 95% of sessions never query history -- always-on tools pay 5-8k tokens per session regardless. Historian pays 0 tokens idle, 500-2k per query, saving ~475k tokens over 100 sessions. Known issues: creates stub session files that break --continue, worker daemon version conflicts, security hooks blocking valid edits.

deja -- Python skill that indexes sessions by episodes and accomplishments. Uses weighted signal ranking (todos > files > text). Requires Python and TodoWrite integration.

conversation-search -- Rust MCP server using Tantivy BM25 full-text search. Fast indexing (~1000 conversations/second) but requires Rust toolchain and persistent disk index.

desktop

Note: Claude Desktop stores conversations server-side, not locally. The local LevelDB files (~/Library/Application Support/Claude/) contain only session tokens, UI preferences, and Intercom state - not conversation content. Claude Desktop support is also blocked by LevelDB locks and Electron sandboxing.

This means local history search for Claude Desktop is not currently possible. This project focuses on Claude Code, which stores full conversation history locally in ~/.claude/projects/.

You may get some Claude Desktop from Claude Code, but only when the Claude app is closed. Furthermore A DXT package and build is available for future compatibility; further investigations are ongoing. Feel free to test with it.

development

git clone https://github.com/Vvkmnn/claude-historian-mcp && cd claude-historian-mcp
npm install && npm run build
npm test

Package requirements:

• Node.js: >=20.0.0 (ES modules)
• Runtime: @modelcontextprotocol/sdk
• Zero external databases -- works with npx

Development workflow:

npm run build          # TypeScript compilation with executable permissions
npm run dev            # Watch mode with tsc --watch
npm run start          # Run the MCP server directly
npm run lint           # ESLint code quality checks
npm run lint:fix       # Auto-fix linting issues
npm run format         # Prettier formatting (src/)
npm run format:check   # Check formatting without changes
npm run typecheck      # TypeScript validation without emit
npm run test           # Lint + type check
npm run prepublishOnly # Pre-publish validation (build + lint + format:check)

Git hooks (via Husky):

• pre-commit: Auto-formats staged .ts files with Prettier and ESLint
• pre-push: Runs full validation (format, lint, type-check, build) before push

Contributing:

• Fork the repository and create feature branches
• Test with large conversation histories before submitting PRs
• Follow TypeScript strict mode and MCP protocol standards

Learn from examples:

• Official MCP servers for reference implementations
• TypeScript SDK for best practices
• Creating Node.js modules for npm package development

license

Appius Claudius Caecus in the Senate by Cesare Maccari (1888). Roman statesman and father of Latin prose.