claude-historian-mcp and Trove

These are **complements**: the historian tool provides conversation-specific retrieval within Claude, while Trove offers broader semantic search across heterogeneous content sources (GitHub, files, screenshots, videos), so users might employ both for different search scopes—conversation history versus external knowledge bases.

claude-historian-mcp
60
Established
Trove
24
Experimental
Maintenance 13/25
Adoption 10/25
Maturity 24/25
Community 13/25
Maintenance 13/25
Adoption 0/25
Maturity 9/25
Community 2/25
Stars: 216
Forks: 17
Downloads:
Commits (30d): 0
Language: TypeScript
License: MIT
Stars:
Forks: 1
Downloads:
Commits (30d): 0
Language: TypeScript
License: MIT
No risk flags
No Package No Dependents

About claude-historian-mcp

Vvkmnn/claude-historian-mcp

📜 An MCP server for conversation history search and retrieval in Claude Code

Implements an MCP server that indexes Claude Code conversation history locally using search algorithms—no external dependencies or databases—enabling semantic retrieval across 11 scopes (conversations, errors, files, tools, plans, config, memories, and more). Provides two core tools: `search` with filtering by project, timeframe, and detail level, and `inspect` for session summaries with focus options on files, tools, or solutions. Integrates with Claude Code via stdio transport and optionally pairs with a companion skill and plugin ecosystem for proactive history checks before web searches and error handling.

About Trove

antoinebecker10-afk/Trove

🦞 Your content. All of it. Semantic search across GitHub, files, screenshots, videos — one index, one search bar. MCP server for Claude Code.

Scores updated daily from GitHub, PyPI, and npm data. How scores work