claude-session-manager
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_sessionB | Rename a session by adding a title prefix to the first message |
| delete_sessionB | Delete a session (moves to .bak folder for recovery) |
| delete_messageB | 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 |
| start_guiC | 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 9 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, clear_sessions deletes sessions, delete_message removes a specific message, delete_session archives a session, list_projects and list_sessions provide different listing scopes, preview_cleanup shows what would be cleaned, rename_session modifies a session name, and start_gui/stop_gui control the GUI server. The descriptions reinforce these distinctions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case, such as clear_sessions, delete_message, list_projects, and start_gui. This predictable naming convention makes the tool set easy to navigate and understand, with no deviations in style or structure across the nine tools.
With 9 tools, the count is well-scoped for session management, covering core operations like listing, deleting, renaming, and GUI control. Each tool earns its place by addressing specific needs in the domain, avoiding bloat while providing comprehensive functionality for managing Claude sessions and projects.
The tool set offers strong coverage for session management, including CRUD-like operations (list, delete, rename) and GUI control. Minor gaps exist, such as no explicit tool for creating new sessions or editing session content beyond renaming, but agents can likely work around these with existing tools like start_gui for manual creation or delete_message for modifications.