The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
ClaudeHistoryMCP
MCP server for searching and surfacing Claude Code conversation history
Install
claude mcp add claude-history -- node "/path/to/ClaudeHistoryMCP/dist/index.js"Install command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →Claude History MCP
An MCP server that makes your Claude Code conversation history searchable and proactively useful. Indexes all past sessions with hybrid BM25 + TF-IDF search, extracts knowledge (decisions, solutions, error fixes), and auto-injects project context at session start.
What it does
Claude Code stores full conversation transcripts as JSONL files in ~/.claude/projects/. This MCP server indexes them and provides 6 tools:
| Tool | Purpose |
|---|---|
search_history |
Full-text search across all conversations with filter syntax |
find_solutions |
Find how you fixed errors/problems before |
get_session_summary |
Structured summary of any session |
list_projects |
List all projects with session counts and dates |
find_patterns |
Discover recurring topics, workflows, and issues |
get_project_context |
Full project context (recent sessions, decisions, knowledge) |
cloud_sync_push |
Push knowledge and sessions to cloud server |
cloud_sync_pull |
Pull knowledge and sessions from cloud server |
cloud_sync_status |
Check cloud sync configuration and connection |
Key features
- Hybrid search: BM25 (keyword precision) + TF-IDF (semantic recall) fused with Reciprocal Rank Fusion
- Filter syntax:
project:name,before:7d,after:2024-01-15,tool:Bash - Knowledge extraction: Automatically extracts decisions, solutions, and error→fix patterns from conversations
- Proactive context: Session-start hook injects relevant project history into new sessions
- Incremental indexing: File watcher detects new/changed sessions and re-indexes automatically
- Fast: Index build ~9s for 170 sessions, searches <200ms
How it works
┌──────────────────────────────────────────────────────┐
│ ClaudeHistoryMCP │
├──────────────┬───────────────┬───────────────────────┤
│ MCP Server │ /claude-history │ SessionStart Hook │
│ (6 tools) │ Skill │ (auto-context) │
├──────────────┴───────────────┴───────────────────────┤
│ Hybrid Search Engine │
│ BM25 (keywords) + TF-IDF (semantic) │
├──────────────────────────────────────────────────────┤
│ Indexing Pipeline │ Knowledge Layer │ Summaries │
├──────────────────────────────────────────────────────┤
│ JSONL Parsers │ File Watcher │ Document Store │
└──────────────────────────────────────────────────────┘
↕ ↕
~/.claude/history.jsonl ~/.claude/projects/*/*.jsonl
Search engine
- Tokenizer: lowercase → strip markdown → split → remove stop words → Porter stem → bigrams
- BM25: Inverted index for keyword precision (Okapi BM25, k1=1.2, b=0.75)
- TF-IDF: Sparse vectors + cosine similarity for semantic recall
- Fusion: Reciprocal Rank Fusion (RRF) combining both rankings
- Boosting: recency (7d=1.2x, 30d=1.1x) + project-match (1.3x if cwd matches)
Knowledge extraction
When sessions end (file stops changing for 5+ minutes), the system automatically extracts:
- Decisions: "decided to", "going with", "chose" patterns
- Solutions: "fixed", "solved", "the issue was" patterns
- Error fixes: error → resolution sequences
Data storage
Runtime data stored at ~/.claude-history-mcp/:
Similar plugs
Reverse engineer anything with agents, from app behavior down to native binaries.
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype…
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io