cc-tap
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sessionsA | List all Claude Code sessions. Args: status_filter: Optional filter — 'active' (non-archived), 'running', 'idle', or '' for all. |
| get_session_infoA | Get details about a specific Claude Code session. Args: session_id: The session ID (with or without 'session_' prefix). |
| read_sessionA | Read recent conversation from a Claude Code session. Args: session_id: The session ID. last_n: Number of recent events to return (default 20). |
| get_session_eventsA | Get raw events from a session, optionally filtered by type. Args: session_id: The session ID. event_types: Comma-separated types to filter (e.g. 'user,assistant'). Empty for all. last_n: Number of recent events to return (default 50). |
| send_messageC | Send a message to a Claude Code session. Args: session_id: The session ID to send to. message: The message text to send. |
| send_and_waitA | Send a message to a Claude Code session and wait for the full response. Polls until the session produces a result event (turn complete), then returns the assistant's response. Use this when you need the other session's answer. Args: session_id: The session ID to send to. message: The message text to send. timeout: Max seconds to wait for a response (default 120). poll_interval: Seconds between polls (default 1.5). |
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 6 tools
Tools are generally distinct: get_session_info, list_sessions, and send_message/send_and_wait have clear purposes. However, get_session_events and read_session both retrieve session content, with descriptions that partially overlap (events vs conversation), which could cause minor confusion.
All tools use a consistent verb_noun pattern in snake_case, such as get_session_info, list_sessions, send_message. The naming is predictable and follows a clear convention.
With 6 tools, the server is well-scoped for managing Claude Code sessions. The count covers essential operations without being excessive, though a tool for archiving or deleting sessions might be expected.
The tool set covers listing, reading, and sending to sessions, but lacks tools for lifecycle management like creating, archiving, or closing sessions. This leaves some gaps for full session management.