$ loading_
Programmatically manage tmux sessions, windows, and panes for terminal automation.
This tool declares no required secrets and no remote network endpoints, and it is an auditable open-source MIT project, so overall risk is relatively low. However, its core capability is programmatic control of tmux, which can affect local terminal sessions and access data within them, so it should be granted carefully.
The materials explicitly state that no keys or environment variables are required. There is no request for API tokens, account credentials, or other sensitive secrets, so credential exposure risk appears low.
The materials declare no remote endpoints, and the description only covers local tmux session management. There is no factual indication of user data being sent to external services or unknown hosts.
The system checks indicate this tool can execute code/start processes, and its function is to create, manage, and interact with tmux sessions, windows, and panes. This means it can affect the local terminal command-execution environment, which is a typical high-privilege capability for this kind of MCP tool and should be scoped carefully.
By interacting with tmux sessions and panes, the tool would typically have visibility into terminal output, historical content, and the local task context inside those sessions. There is no evidence of permissions beyond its stated purpose, but access to data within tmux itself warrants caution.
The source is a third-party registry, but the repository is open source under the MIT license, making the code theoretically auditable, which is a clear risk-reducing factor. However, it has 0 stars and unknown maintenance status, so stronger trust signals are lacking and the code and dependencies should be reviewed before deployment.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "tmux-mcp" yet — see the docs or source repo.
Use tmux-mcp to create a tmux session named app-dev: run the frontend dev server in the first window, the backend API in the second, and split the third window into two panes for log watching and test commands.
A ready-to-use tmux session layout with the requested commands started in each window or pane.
Use tmux-mcp to create a monitoring session with one pane for each of 4 servers, then run SSH login and resource monitoring commands in each pane so I can view their status together.
A centralized tmux monitoring session showing multiple servers, with one pane assigned to each machine.
Use tmux-mcp to restore my data analysis terminal environment: create a session named analysis, with one window for Jupyter, one for the database connection, and another for running Python scripts.
A tmux session organized for the analysis workflow, ready for continued data work and experiments.
Run commands and control a persistent tmux terminal session remotely.
Control Neovim in tmux so AI can automate editing and development tasks.
Let AI safely control tmux sessions, windows, and panes for terminal automation.
Let AI run commands in a shared tmux terminal with live human visibility.
Control a persistent terminal via MCP for commands, SSH, and containers.
Create interactive terminal canvases inside AI coding assistants for structured workflows.