claude-code-session-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_PROJECTS_DIR | No | Path to the directory containing Claude Code session transcripts. Overrides the default of ~/.claude/projects. | ~/.claude/projects |
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 |
|---|---|
| list_sessionsA | List past Claude Code sessions, newest first, with the project, time span, number of turns and prompts, per-model token usage and a tally of which tools were called. Use it to answer questions like which projects were worked on last week or which session was the long one. Returns counts only, never the text of any message. |
| session_statsA | Full counts for a single session id: duration in seconds, turns, prompts, subagent turns, damaged lines, per-model token usage and the combined totals. Take the id from list_sessions. Returns counts only, never the text of any message. |
| tool_usageA | Count how often each Claude Code tool (Read, Edit, Bash, Grep and the rest) was called across the sessions matching the filters, most used first. Use it to answer questions about working habits, such as how much of a week was reading versus editing. Returns tool names and counts, never tool arguments. |
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 3 tools
Each tool has a distinctly separate purpose: list_sessions provides an overview for browsing, session_stats drills into a single session's aggregate counts, and tool_usage analyzes tool call frequencies across sessions. There is no overlap or ambiguity in what each tool returns.
list_sessions follows a verb-noun pattern, while session_stats and tool_usage are noun-noun, but all use consistent snake_case and are immediately readable. The slight variation is predictable and does not cause confusion.
With only three tools, the server is tightly scoped to session statistics and aggregation. This count is well within the ideal 3-15 range, and each tool serves a necessary, non-redundant function for the stated purpose.
The tool set fully covers the intended workflow: listing sessions, viewing detailed stats for a specific session, and aggregating tool usage across sessions. The deliberate omission of message content is consistent with the server's focus on counts, leaving no obvious gaps.