tmux-shell
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_tmux_paneA | Reads the content of a tmux pane. This enables AI agents to see what is currently displayed in the terminal, providing context-aware assistance during interactive sessions (e.g., git rebase, vim, conflict resolution). The agent only reads the pane when explicitly invoked - there is no background monitoring. |
| list_tmux_sessionsA | Lists all available tmux sessions, windows, and panes. Use this to discover available targets before calling read_tmux_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 2 tools
The two tools have clearly distinct purposes: one lists available sessions/windows/panes, and the other reads the content of a specific pane. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern: list_tmux_sessions and read_tmux_pane, using snake_case throughout.
With only two tools, the server is on the low end of the appropriate range. While it may serve a narrow read-only use case, it feels thin for a tmux interaction server.
The server lacks essential tools for writing commands, managing sessions (create, attach, close), or any interactive control. This is a significant gap for a terminal-focused server.