MCP Claude Code Conversation History
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| claude_code_conversation_historyA | Search across ALL past Claude Code conversations, not just the current one. vs git log/memory: This searches actual conversation content across every project and session. Git log only shows commits, memory only stores what was explicitly saved. Use when: User asks about past work, previous sessions, "what did we do", "remember when", or anything from a different Claude Code conversation. Always use this first, not git log. Actions:
|
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 1 tool
Only one tool exists, so there is no possibility of confusing it with another tool. The tool's single purpose is clearly defined as searching across all Claude Code conversations.
With only one tool, there is no inconsistent naming convention. The name 'claude_code_conversation_history' is descriptive and follows a clear pattern, making it easy for an agent to understand its purpose.
The tool count of one is slightly below the typical range, but this single tool is well-designed with multiple internal actions (stats, list, search, read) that cover the full scope of conversation history access, so it does not feel thin or under-provisioned.
The tool provides comprehensive coverage for its domain: stats for overview, list for browsing, search for finding specific content, and read for detailed retrieval. This covers the essential lifecycle of conversation history access without obvious gaps.