Claude Historian▌
by vvkmnn
Claude Historian is a free AI search engine offering advanced search, file context, and solution discovery in Claude Cod
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.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Developers using Claude Code regularly
- / Finding past solutions to recurring problems
- / Tracking changes and context for specific files
- / Learning from previous coding patterns
capabilities
- / 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
what it does
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.
about
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
MIT
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.
readme
 [](https://www.npmjs.com/package/claude-historian-mcp) [](https://opensource.org/licenses/MIT) [](https://www.typescriptlang.org/) [](https://nodejs.org/) [](#) [](https://github.com/Vvkmnn/claude-historian-mcp)  --- ## install **Requirements:** [](https://claude.ai/code) **From shell:** ```bash 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.) ```json { "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: ```bash 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`. ## [skill](.claude/skills/claude-historian) Optionally, install the skill to teach Claude when to proactively use historian: ```bash 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](https://github.com/Vvkmnn/claude-emporium) For automatic history search with hooks and commands, install from the [claude-emporium](https://github.com/Vvkmnn/claude-emporium) marketplace: ```bash /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
FAQ
- What is the Claude Historian MCP server?
- Claude Historian is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Claude Historian?
- This profile displays 30 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.8 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.8★★★★★30 reviews- ★★★★★Min Rao· Dec 8, 2024
We evaluated Claude Historian against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Neel Park· Nov 27, 2024
Claude Historian is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Liam White· Nov 27, 2024
According to our notes, Claude Historian benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Neel Shah· Oct 18, 2024
Strong directory entry: Claude Historian surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Alexander Sanchez· Oct 18, 2024
We wired Claude Historian into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Sakshi Patil· Sep 25, 2024
Strong directory entry: Claude Historian surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Neel Ndlovu· Sep 25, 2024
I recommend Claude Historian for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Rahul Santra· Sep 21, 2024
According to our notes, Claude Historian benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Tariq Flores· Sep 1, 2024
Claude Historian reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Nikhil Verma· Aug 20, 2024
I recommend Claude Historian for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 30