tmux-bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIMI_PATH | No | Path to kimi binary (kimi-tmux only) | |
| TMUX_BRIDGE_SOCKET | No | Override tmux server socket path |
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_listA | List all tmux panes with target ID, process, label, and working directory |
| tmux_readA | Read the last N lines from a tmux pane. Must be called before type/keys (read guard). Target can be a pane ID (%N), session:window.pane, or a label. |
| tmux_typeA | Type text into a tmux pane WITHOUT pressing Enter. You must tmux_read the pane first (read guard enforced). After typing, use tmux_read to verify, then tmux_keys to press Enter. |
| tmux_messageA | Send a message to another agent's pane with auto-prepended sender info, reply target, and correlation ID. Cannot message your own pane (loop prevention). Must tmux_read first. |
| tmux_keysA | Send special keys to a tmux pane (Enter, Escape, C-c, etc.). Must tmux_read first. |
| tmux_nameB | Label a tmux pane for easy addressing (e.g., 'gemini', 'claude'). The label appears in the tmux border. |
| tmux_resolveC | Look up a pane's target ID by its label |
| tmux_idA | Print the current pane's tmux ID ($TMUX_PANE). Useful for self-identification when labeling. |
| tmux_doctorA | Diagnose tmux connectivity issues — checks socket, env vars, and pane visibility |
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
Each tool targets a distinct action on tmux panes: labeling, resolving, listing, reading, typing, sending keys, messaging, diagnostics. No two tools overlap in purpose, and the read guard enforces a clear workflow without ambiguity.
All tools follow the 'tmux_' prefix with a concise verb: tmux_name, tmux_resolve, tmux_id, tmux_doctor, tmux_list, tmux_read, tmux_type, tmux_message, tmux_keys. The pattern is uniform and predictable.
With 9 tools, the server covers all core interactions with tmux panes (label, identify, list, read, type, key, message) plus diagnostics. This is a well-scoped set—neither too few nor too many.
The tools cover the essential CRUD-like operations for tmux panes: reading, writing (type/keys), labeling, and listing. Missing would be creating new panes or advanced flush/wait operations, but these are outside the server's stated scope as a bridge.