tmux-mcp
Related Servers
Alternatives to tmux-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to manage local tmux sessions, including creating and controlling sessions, windows, and panes, sending commands, and capturing terminal output.167 npmDo What The F*ck You Want To Public
- AlicenseAqualityDmaintenanceAllows AI assistants to create, manage, and interact with tmux sessions, windows, and panes programmatically.1936 PyPIMIT
- AlicenseAqualityDmaintenanceEnables AI agents to spawn, interact with, and orchestrate multiple concurrent terminal sessions via tmux.9MIT
- FlicenseNot gradedqualityDmaintenanceExposes tmux features to AI agents for managing sessions, windows, and panes with built-in command execution. It includes comprehensive guardrails to prevent destructive system operations, file deletions, and unauthorized network changes.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create and interact with isolated tmux terminal sessions in real time, supporting command execution, output capture, and session management.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents running in separate tmux panes to read each other's output, send tasks and messages across panes, and coordinate multi-agent workflows through standard MCP tool calls. It calls tmux directly with no external dependencies beyond tmux itself.49 npmMIT
TDQS
Scored across 6 tools
The session lifecycle tools (list_sessions, new_session, kill_session) are clearly distinct, and capture is a read-only pane operation. exec and send_keys both send input, but their descriptions distinguish shell-command execution with waiting from raw key/literal input without shell interpretation.
The names are all lowercase snake_case and readable, but they mix full verb_noun session operations (list_sessions, new_session, kill_session) with bare verbs (exec, capture) and a different verb phrase (send_keys). The convention is understandable but not fully predictable across the set.
Six tools is well within a practical range for a tmux control server, and each tool maps to a necessary capability: session discovery, creation, termination, command execution, raw input, and output capture. No tool appears redundant or filler-like.
The core tmux workflow is covered: list/create/kill sessions, run commands, send keys, and capture output. Some secondary operations are absent, such as renaming sessions or explicit window/pane management, but agents can work around many of these via exec and send_keys.