oracle-tmux-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
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 |
|---|---|
| tmux_register_agentB | Register an agent and ensure its live tmux pane exists. Not required before send/broadcast — they self-provision — but useful to pre-create a pane before anyone messages that agent. |
| tmux_sendB | Send a message to one agent. Appears instantly in the recipient's tmux pane (push-based, no polling) and is recorded in their queryable history. |
| tmux_broadcastC | Send a message to every registered agent (except the sender). Each recipient's pane updates instantly. |
| tmux_list_agentsA | List every agent registered in the mesh. |
| tmux_historyA | Fetch an agent's structured message history (source of truth — the tmux pane is just a live view of the same data). |
| tmux_open_claudeA | Spawn an interactive Claude Code session in a tmux pane as the given agent. From then on, tmux_send to that agent types the message directly into that chat — it appears on screen and Claude responds, no polling and no human input. |
| tmux_attach_infoA | Get the shell command a human can run to attach a terminal directly to one agent's live pane. |
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 7 tools
Each tool targets a clearly distinct operation: registration, unicast, broadcast, listing, history, interactive session spawning, and attach info. There is no meaningful overlap or confusion between any two tools.
All tools follow a consistent tmux_verb_noun pattern (tmux_register_agent, tmux_send, tmux_broadcast, tmux_list_agents). The naming convention is uniform and predictable throughout.
Seven tools is a well-scoped set for a messaging/orchestration mesh. Each tool earns its place, covering registration, messaging (unicast/broadcast), introspection, interactive session management, and operational info.
The surface covers the core lifecycle well: register, message, broadcast, list, view history, and open interactive sessions. Minor gaps exist (no explicit unregister/deregister or kill-session tool), but agents can still operate without these.