
Claude Historian
Searches your Claude Code conversation history to find past solutions, track file changes, and discover patterns from previous coding sessions. Parses JSONL logs to provide intelligent search across your development work.
Provides intelligent search capabilities across Claude Code conversation history with specialized tools for conversation search, file context discovery, error solution patterns, and session management through JSONL log parsing and AI-enhanced query expansion.
What it does
- Search through Claude Code conversation history
- Find all conversations related to specific files
- Discover solutions to similar errors from past sessions
- Extract summaries from conversation sessions
- Analyze tool usage patterns and workflows
- Browse recent coding sessions with activity summaries
Best for
About Claude Historian
Claude Historian is a community-built MCP server published by vvkmnn that provides AI assistants with tools and capabilities via the Model Context Protocol. Claude Historian is a free AI search engine offering advanced search, file context, and solution discovery in Claude Cod It is categorized under developer tools. This server exposes 7 tools that AI clients can invoke during conversations and coding sessions.
How to install
You can install Claude Historian in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
Claude Historian is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Tools (7)
Search through Claude Code conversation history
Find conversations related to a specific file
Find previous similar questions or queries
Find how similar errors were resolved in the past
List recent conversation sessions
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-historiantoclaude-historian-mcp. Existing users should update your install command and MCP config args toclaude-historian-mcp.
skill
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 manageme
README truncated. View full README on GitHub.
Alternatives
Related Skills
Browse all skillsIntegrate Claude Agent SDK with You.com HTTP MCP server for Python and TypeScript. Use when developer mentions Claude Agent SDK, Anthropic Agent SDK, or integrating Claude with MCP tools.
Production-ready financial analyst skill with ratio analysis, DCF valuation, budget variance analysis, and rolling forecast construction. 4 Python tools (all stdlib-only). Works with Claude Code, Codex CLI, and OpenClaw.
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.
Syncs Claude Skills with other AI coding tools like Cursor, Copilot, and Codeium by creating cross-references and shared knowledge bases. Invoke when user wants to leverage skills across multiple tools or create unified AI context.
This skill allows Claude to conduct comprehensive security audits of code, infrastructure, and configurations. It leverages various tools within the security-pro-pack plugin, including vulnerability scanning, compliance checking, cryptography review, and infrastructure security analysis. Use this skill when a user requests a "security audit," "vulnerability assessment," "compliance review," or any task involving identifying and mitigating security risks. It helps to ensure code and systems adhere to security best practices and compliance standards.