TmuxBLOCK
A MCP server for our beloved terminal multiplexer tmux.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Model Context Protocol server that enables Claude Desktop to interact with and view tmux session content. This integration allows AI assistants to read from, control, and observe your terminal sessions.
Features
- List and search tmux sessions
- View and navigate tmux windows and panes
- Capture and expose terminal content from any pane
- Execute commands in tmux panes and retrieve results (use it at your own risk ⚠️)
- Create new tmux sessions and windows
- Split panes horizontally or vertically with customizable sizes
- Kill tmux sessions, windows, and panes
Check out this short video to get excited!
[](https://www.youtube.com/watch?v=3W0pqRF1RS0)
Prerequisites
- Node.js
- tmux installed and running
Usage
Configure Claude Desktop
Add this MCP server to your Claude Desktop configuration:
"mcpServers": {
"tmux": {
"command": "npx",
"args": ["-y", "tmux-mcp"]
}
}MCP server options
You can optionally specify the command line shell you are using, if unspecified it defaults to bash
"mcpServers": {
"tmux": {
"command": "npx",
"args": ["-y", "tmux-mcp", "--shell-type=fish"]
}
}The MCP server needs to know the shell only when executing commands, to properly read its exit status.
Available Resources
tmux://sessions- List all tmux sessionstmux://pane/{paneId}- View content of a specific tmux panetmux://command/{commandId}/result- Results from executed commands
Available Tools
list-sessions- List all active tmux sessionsfind-session- Find a tmux session by namelist-windows- List windows in a tmux sessionlist-panes- List panes in a tmux windowcapture-pane- Capture content from a tmux panecreate-session- Create a new tmux sessioncreate-window- Create a new window in a tmux sessionsplit-pane- Split a tmux pane horizontally or verticall
5e945414196aOBSERVED · 2026-10-05Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add tmux-mcp -- npx -y [email protected]
{
"mcpServers": {
"tmux-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (13)
7 read · 3 write · 3 destructive. Blast radius: 3 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
capture-pane | read | Capture content from a tmux pane with configurable lines count and optional color preservation |
create-session | write | Create a new tmux session |
create-window | write | Create a new window in a tmux session |
execute-command | write | Execute a command in a tmux pane and get results. For interactive applications (REPLs, editors), use |
find-session | read | Find a tmux session by name |
get-command-result | read | Get the result of an executed command |
kill-pane | destructive | Kill a tmux pane by ID |
kill-session | destructive | Kill a tmux session by ID |
kill-window | destructive | Kill a tmux window by ID |
list-panes | read | List panes in a tmux window |
list-sessions | read | List all active tmux sessions |
list-windows | read | List windows in a tmux session |
split-pane | read | Split a tmux pane horizontally or vertically |
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- declared (1 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (3)
const { stdout } = await exec(`tmux ${tmuxCommand}`);kill-pane, kill-session, kill-window
@modelcontextprotocol/sdk, uuid, zod, @types/node, @types/uuid, typescript
Gates applied: no_behavioural_pass.
5e945414196afull audit observations/trust-audit/mcp-server/nickgnd__tmux.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-05 | 5e945414196a | BLOCK | D | 69 | first audit |
Questions
What is the Tmux MCP server?
A MCP server for our beloved terminal multiplexer tmux.
What tools does Tmux expose?
13 in total: 7 read-only, 3 that write, and 3 that can delete or overwrite (kill-pane, kill-session, kill-window). Every one is listed on this page with its risk.
Is Tmux safe to connect to an agent?
No — not without reading the findings first. The audit graded it D (69/100) and found 1 critical or high issue in the source. Each one is listed on this page with the file and line it is on. Separately from the audit: 3 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Tmux need?
No credential environment variables were found in its source, so it appears to need none.
How does Tmux run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as tmux-mcp at 0.2.2.
How current is this page?
The grade is for one exact copy of the source (5e945414196a), read on 2026-10-05. The repository is watched and re-audited when it changes.