Tmux MCP Server: agent access to tmux sessions
Tmux MCP Server
An MCP server that lets an agent read tmux panes, run commands in them and create sessions while you watch the output
- 305 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The execute-command tool runs arbitrary commands in a tmux pane with your user's rights
- The agent can kill sessions, windows and panes, interrupting processes running there
- Pane capture exposes everything printed in the terminal, including secrets and tokens
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/tmux-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The execute-command tool runs arbitrary commands in a tmux pane with your user's rights
- The agent can kill sessions, windows and panes, interrupting processes running there
- Pane capture exposes everything printed in the terminal, including secrets and tokens
This is third-party code. Review the repository files before installing.
What it does
Tmux MCP Server connects an agent to a tmux that is already running. The agent sees the list of sessions, windows and panes, finds a session by name and captures text from any pane. That is how it reads the output of long processes, server logs or running tests without you copying them by hand. Beyond reading, the server can act. The `execute-command` tool runs a command in a chosen pane, and `get-command-result` returns its outcome by ID. The agent can create sessions and windows, split a pane horizontally or vertically at a given size, and kill sessions, windows and panes. The server also exposes the same data as three MCP resources: the session list, pane content and a command's outcome.
Who it is for. For developers who keep servers, builds and logs in tmux and want an agent to see them and run commands in the same windows.
Good fit when
- A build or tests run in one pane and the agent must read the errors without you pasting them
- You want the agent to run a command in an open session and show the result
- A task needs a laid-out environment: create a session, split the window into panes and start a server and a client in them
- You want to watch the terminal yourself while the agent works in the same pane
- You need to find a session by name among several running ones
Not a fit when
- You only need to run one command: an agent's own terminal is enough for that
- The environment has no tmux or it is not running: the server needs a live tmux
- Sessions hold production servers or privileged shells the agent should not reach
- You work unattended: the tool kills sessions and runs arbitrary commands
Example request
Look at the tests pane in the dev session, find the failing test and tell me what the error is.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
Node.js and an installed, running tmux are required. The server takes the shell into account only when it runs commands, reading the exit status from it. If you work in fish, set --shell-type, otherwise bash is assumed.
The author calls command execution plainly a matter of your own risk: the server asks for no confirmation. A pane capture hands the agent everything printed in the terminal. The repository was last updated in February 2026.
How to disable. Remove the tmux entry from the mcpServers block in the client config and restart it. Running tmux sessions stay as they were.
FAQ
How do I connect Tmux MCP Server?
Add a tmux entry to the mcpServers block of your client config with the command npx and the arguments -y and tmux-mcp, then restart the client. No separate install or keys are needed, only a running tmux.
Which tools does the server have?
Thirteen: list-sessions, find-session, list-windows, list-panes, capture-pane, create-session, create-window, split-pane, kill-session, kill-window, kill-pane, execute-command and get-command-result.
What is the --shell-type argument for?
The server uses the shell when it runs a command in a pane so it can read the exit status correctly. The default is bash; for fish set the value explicitly.
Is it safe to allow the agent execute-command?
The tool runs arbitrary commands in the chosen pane with your user's rights. Approve calls by hand and do not keep privileged shells open in these sessions.
Which MCP resources does the server expose?
Three: `tmux://sessions` with the session list, `tmux://pane/{paneId}` with pane content and `tmux://command/{commandId}/result` with a command's result.
Discussion
No questions or reviews yet.
Related
MCP serversSSH MCP Server (classfang): remote commands over SSH
SSH MCP Server (classfang)
An SSH MCP server: the agent runs commands, reads and writes files over SFTP, transfers files and starts long jobs while credentials stay with you
A secure MCP runtime through which an agent operates local machines, servers and containers
Self-hosted MCP server for running commands on remote servers over SSH, with tokens and roles
A self-hosted gateway that merges several MCP servers into one endpoint with auth and tool selection
A Node.js manager for MCP servers: it starts local servers, connects remote ones and gives a client one address, with a REST API for control
MCP SSH Manager
mcp-ssh-manager
Managing several SSH connections from Claude Code and Codex: commands, file transfer, databases and backups
README in short
The page is short: features, requirements and a Claude Desktop setup example, then the resources and the tool list. A demo video comes with the description.