claude-sessions-mcp
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 |
|---|---|
| list_projectsB | List all Claude Code projects with session counts |
| list_sessionsC | List all sessions in a project |
| rename_sessionC | Rename a session by adding a title prefix to the first message |
| delete_sessionB | Delete a session (moves to .bak folder for recovery) |
| delete_messageC | Delete a message from a session and repair the parentUuid chain |
| preview_cleanupC | Preview sessions that would be cleaned (empty and invalid API key sessions) |
| clear_sessionsB | Delete all empty sessions and invalid API key sessions |
| get_session_filesB | Get list of all files changed in a session (from file-history-snapshot and tool_use) |
| get_session_diffC | Get diff summary for a session including file changes and snapshot info |
| split_sessionB | Split a session at a specific message, creating a new session with messages from that point onwards |
| start_guiB | Start the web GUI for session management and open it in browser |
| stop_guiB | Stop the web GUI server |
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 12 tools
Most tools have clearly distinct purposes targeting different session management operations, with good separation between listing, deletion, modification, and GUI control. However, clear_sessions and preview_cleanup have some conceptual overlap around session cleanup, though their descriptions clarify that one previews while the other executes.
All tools follow a consistent verb_noun naming pattern with snake_case throughout. The verbs are appropriately descriptive (list, get, delete, rename, split, start, stop) and consistently applied to their respective nouns (sessions, projects, messages, GUI).
12 tools is well-scoped for a session management system, covering core operations without bloat. Each tool serves a distinct purpose in the session lifecycle from creation/listing to modification/deletion, with GUI management as a logical extension.
The toolset provides comprehensive coverage of session management including CRUD operations (list, delete, rename), content manipulation (delete_message, split_session), and analysis (get_session_diff, get_session_files). The main gap is the lack of a tool to create new sessions, though agents could work around this by using the GUI or external methods.