Claude Historian
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_conversationsC | Search through Claude Code conversation history with smart insights |
| find_file_contextB | Find all conversations and changes related to a specific file |
| find_similar_queriesB | Find previous similar questions or queries with enhanced matching |
| get_error_solutionsB | Find solutions for specific errors with enhanced matching |
| list_recent_sessionsC | Browse recent sessions with smart activity detection and summaries |
| extract_compact_summaryC | Get intelligent summary of a conversation session with key insights |
| find_tool_patternsC | Analyze tool usage patterns, workflows, and successful practices |
| search_plansB | Search Claude Code plan files for past implementation approaches, decisions, and patterns |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes, such as extract_compact_summary for session summaries and find_file_context for file-related conversations. However, find_similar_queries and search_conversations could potentially overlap in functionality, as both involve searching through conversation history, which might cause minor confusion for an agent.
All tool names follow a consistent verb_noun pattern with snake_case, such as extract_compact_summary, find_file_context, and search_conversations. This predictability makes it easy for an agent to understand and navigate the tool set without naming-related confusion.
With 8 tools, the server is well-scoped for its purpose of analyzing conversation history and patterns. Each tool appears to serve a specific function, such as summarizing sessions, finding errors, or searching plans, making the count appropriate and manageable for the domain.
The tool set covers key aspects of conversation analysis, including summarization, searching, error resolution, and pattern detection. A minor gap might be the lack of tools for modifying or annotating historical data, but the surface is largely complete for querying and insights, allowing agents to work effectively within the domain.