developer-tools

Claude Historian

vvkmnn

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.

github stars

216

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

AI-enhanced query matchingWorks with existing Claude Code logs8 specialized search tools

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

claude-historian-mcp # claude-historian-mcp An [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server for searching your [Claude Code](https://docs.anthropic.com/en/docs/claude-code) conversation history. Find past solutions, track file changes, and learn from previous work.
![claude-historian-mcp](demo/demo.gif) [![npm version](https://img.shields.io/npm/v/claude-historian-mcp.svg)](https://www.npmjs.com/package/claude-historian-mcp) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![TypeScript](https://img.shields.io/badge/TypeScript-007ACC?logo=typescript&logoColor=white)](https://www.typescriptlang.org/) [![Node.js](https://img.shields.io/badge/node-%3E%3D20-brightgreen)](https://nodejs.org/) [![Claude](https://img.shields.io/badge/Claude-D97757?logo=claude&logoColor=fff)](#) [![GitHub stars](https://img.shields.io/github/stars/Vvkmnn/claude-historian-mcp?style=social)](https://github.com/Vvkmnn/claude-historian-mcp) ![CodeRabbit Pull Request Reviews](https://img.shields.io/coderabbit/prs/github/Vvkmnn/claude-historian-mcp?utm_source=oss&utm_medium=github&utm_campaign=Vvkmnn%2Fclaude-historian-mcp&labelColor=171717&color=FF570A&link=https%3A%2F%2Fcoderabbit.ai&label=CodeRabbit+Reviews) --- ## install **Requirements:** [![Claude Code](https://img.shields.io/badge/Claude_Code-555?logo=data:image/svg%2bxml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAxOCAxMCIgc2hhcGUtcmVuZGVyaW5nPSJjcmlzcEVkZ2VzIj4KICA8IS0tIENsYXdkOiBDbGF1ZGUgQ29kZSBtYXNjb3QgLS0+CiAgPCEtLSBEZWNvZGVkIGZyb206IOKWkOKWm+KWiOKWiOKWiOKWnOKWjCAvIOKWneKWnOKWiOKWiOKWiOKWiOKWiOKWm+KWmCAvIOKWmOKWmCDilp3ilp0gLS0+CiAgPCEtLSBTdWItcGl4ZWxzIGFyZSAxIHdpZGUgeCAyIHRhbGwgdG8gbWF0Y2ggdGVybWluYWwgY2hhciBjZWxsIGFzcGVjdCByYXRpbyAtLT4KICA8cmVjdCBmaWxsPSIjZDk3NzU3IiB4PSIzIiAgeT0iMCIgd2lkdGg9IjEyIiBoZWlnaHQ9IjIiLz4KICA8cmVjdCBmaWxsPSIjZDk3NzU3IiB4PSIzIiAgeT0iMiIgd2lkdGg9IjIiICBoZWlnaHQ9IjIiLz4KICA8cmVjdCBmaWxsPSIjZDk3NzU3IiB4PSI2IiAgeT0iMiIgd2lkdGg9IjYiICBoZWlnaHQ9IjIiLz4KICA8cmVjdCBmaWxsPSIjZDk3NzU3IiB4PSIxMyIgeT0iMiIgd2lkdGg9IjIiICBoZWlnaHQ9IjIiLz4KICA8cmVjdCBmaWxsPSIjZDk3NzU3IiB4PSIxIiAgeT0iNCIgd2lkdGg9IjE2IiBoZWlnaHQ9IjIiLz4KICA8cmVjdCBmaWxsPSIjZDk3NzU3IiB4PSIzIiAgeT0iNiIgd2lkdGg9IjEyIiBoZWlnaHQ9IjIiLz4KICA8cmVjdCBmaWxsPSIjZDk3NzU3IiB4PSI0IiAgeT0iOCIgd2lkdGg9IjEiICBoZWlnaHQ9IjIiLz4KICA8cmVjdCBmaWxsPSIjZDk3NzU3IiB4PSI2IiAgeT0iOCIgd2lkdGg9IjEiICBoZWlnaHQ9IjIiLz4KICA8cmVjdCBmaWxsPSIjZDk3NzU3IiB4PSIxMSIgeT0iOCIgd2lkdGg9IjEiICBoZWlnaHQ9IjIiLz4KICA8cmVjdCBmaWxsPSIjZDk3NzU3IiB4PSIxMyIgeT0iOCIgd2lkdGg9IjEiICBoZWlnaHQ9IjIiLz4KPC9zdmc+Cg==)](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 ` Requires the MCP server installed first. See the emporium for other Claude Code plugins and MCPs. ## features [MCP server](https://modelcontextprotocol.io/) 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= > "How did we fix that Redis connection pooling nightmare?" > "Docker container keeps crashing on Kubernetes deployment" > "React infinite re-render loop - useEffect dependency hell" ``` ```json [⌐■_■] 📜 "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= > "package.json changes that broke everything last month" > "When we accidentally committed .env to main branch" > "Authentication service refactor - before/after comparison" ``` ```json [⌐□_□] 📜 "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= > "MODULE_NOT_FOUND - the classic npm/yarn version mismatch" > "CORS preflight failing - but only on production Fridays?" > "Database deadlock during Black Friday traffic spike" ``` ```json [⌐×_×] 📜 "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= > "Database queries slower than my morning coffee brewing" > "How to implement error boundaries without losing sanity" > "State management: Redux vs Zustand vs just useState" ``` ```json [⌐◆_◆] 📜 "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" ``` ```json [⌐○_○] 📜 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= > "Read → Edit → Bash combo for rapid prototyping" > "When I use Grep vs Task for different searches" > "Git operations during feature branch management" ``` ```json [⌐⎚_⎚] 📜 "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= > "How did we architect the authentication system?" > "Database migration strategy from last refactor" > "API versioning approach we decided on" ``` ```json [⌐▣_▣] 📜 "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= > "What are my rules about minimalism and code quality?" > "Find the systematic debugging skill documentation" > "Search for test-driven development guidelines" ``` ```json [⌐◈_◈] 📜 "verify everything" | 2 results { "results": [{ "type": "assistant", "ts": "1/31/2026", "content": "# Verify Everything ## Rule Every claim must be anchored to evidence...", "file": "/Users/v/.claude/rules/verify.md", "category": "global-rules", "score": 34 }] } ``` #### `search_tasks` Search task manageme ---

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. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 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

GET_STARTED →
MCP server reviews

Ratings

4.830 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

1 / 3