mcp-tmux
Related Servers
Alternatives to mcp-tmux
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that gives AI assistants full visibility into your tmux sessions — browse sessions, windows, and panes, read terminal output, and send commands.1457 npm1MIT
- AlicenseAqualityCmaintenanceMCP server for tmux enabling AI assistants to manage tmux sessions, windows, panes, layouts, and execute commands securely through natural language. Supports multiple profiles including read-only and full tool sets.222MIT
- AlicenseNot gradedqualityAmaintenanceA standalone MCP server that lets AI coding agents running in separate tmux panes read each other's output, send messages and keystrokes, and coordinate multi-agent workflows through standard MCP tool calls. It shells out directly to tmux, so no external dependencies beyond tmux itself are required.52 npmMIT
- AlicenseNot gradedqualityAmaintenanceA standalone MCP server that lets AI agents running in separate tmux panes read each other's output, send messages and keystrokes into other panes, and coordinate multi-agent workflows without copy-pasting context. It talks directly to tmux over stdio using standard MCP tool calls such as tmux_read, tmux_message, tmux_keys, and tmux_name.52 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server for tmux operations that provides comprehensive control over tmux sessions, windows, and panes.1-
- AlicenseAqualityDmaintenanceMCP server for terminal control enabling AI to manage terminal sessions via iTerm2 or tmux, with features like screen reading, keyboard/mouse input, and background execution.912 npm22MIT
TDQS
Scored across 71 tools
Each tool targets a specific tmux operation with clear, non-overlapping purposes. Even related tools like tmux_run, tmux_send_keys, and tmux_command have distinct behaviors: run executes and captures output, send_keys sends input, and command runs arbitrary tmux commands. Buffer tools are also clearly differentiated.
All tools follow the consistent 'tmux_verb_noun' pattern in snake_case. Verbs are imperative and predictably describe the action (e.g., list_*, kill_*, set_*, select_*). No mixing of styles or ambiguous abbreviations.
With 71 tools, the set is large and may feel heavy for agents, but it mirrors tmux's extensive command set. The number is reasonable given the server aims to provide comprehensive control of a complex terminal multiplexer, though it exceeds the typical well-scoped range.
The tool surface covers virtually all tmux operations: session, window, pane management; buffer handling; environment, options, hooks, key bindings; copy mode; streaming; and auxiliary commands like version check and server info. No significant gaps are apparent.