teammate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEAMMATE_CODEX_SESSION_ID | No | Optional: explicitly set the iTerm session ID for the Codex pane to pin it (useful when automatic detection fails). | |
| TEAMMATE_CLAUDE_SESSION_ID | No | Optional: explicitly set the iTerm session ID for the Claude pane to pin it (useful when automatic detection fails). |
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 |
|---|---|
| ask_codexB | Ask the Codex pane a question and return its answer. Use this from Claude when you want Codex's opinion, a code review, or to delegate execution to it. |
| ask_claudeA | Ask the Claude pane a question and return its answer. Use this from Codex when you want Claude's plan, design feedback, or a sanity check. |
| broadcastB | Push a message to both panes without waiting for a reply. |
| queue_statusA | Return queue counts + recent completions (debugging). |
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 4 tools
Each tool has a distinct purpose: ask_claude and ask_codex target specific panes, broadcast sends to both without waiting, and queue_status provides debugging info. No overlap.
All tool names use lowercase with underscores and follow a consistent verb_noun pattern (ask_claude, ask_codex, queue_status) or are a clear verb (broadcast).
4 tools is well-scoped for the server's purpose of inter-pane communication, covering questioning each pane, broadcasting, and status monitoring.
Core workflows are covered, but a minor gap exists: there is no tool to send a one-way message to a specific pane without expecting a reply (only broadcast to both).