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.164 npmDo What The F*ck You Want To Public
- FlicenseAqualityDmaintenanceEnables AI agents to spawn, interact with, and orchestrate multiple concurrent terminal sessions via tmux.9-
- FlicenseNot gradedqualityCmaintenanceExposes 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 gradedqualityCmaintenanceEnables AI agents to create and interact with isolated tmux terminal sessions in real time, supporting command execution, output capture, and session management.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to control tmux sessions, manage windows and panes, and search/extract text from terminal output.2MIT
- AlicenseAqualityDmaintenanceEnables programmatic control over tmux terminal sessions for SSH access, command execution, and terminal automation. Supports creating sessions, sending commands, capturing output, and managing multiple panes for interactive debugging and monitoring.88 npmMIT
TDQS
Scored across 19 tools
Most tools have clearly distinct purposes (create, list, read, send, resize, kill). The only potential confusion is between tmux_read_pane (general pane capture) and tmux_read_cc_pane (specialized for Claude Code monitoring), but their descriptions clearly differentiate them. Remote bash tools are clearly separated by the remote_bash_ prefix.
All tools use consistent verb_noun snake_case with a domain prefix (tmux_, remote_bash_). The pattern is highly predictable (list_*, create_*, rename_*, select_*, etc.) across the entire set.
At 19 tools, the set is slightly heavy for a single server, especially since 4 tools handle remote SSH (a separate domain). The tmux-specific tools alone (15) would be well-scoped; adding remote_bash pushes it into the borderline range.
The tmux lifecycle is fully covered: create, list, read, update, and delete for sessions, windows, and panes, plus send_keys, split, and resize. The remote_bash set is also complete with connect, execute, disconnect, and list. There are no obvious dead ends.