tmux-mcp server

Read from the package source without running it. The installed server may list more.

• capture_pane

  Capture current output of a tmux pane. Target format: 'session:window.pane' (e.g. 'work:0.0'). Use list_sessions → list_windows → list_panes to build the target. WARNING: pane output may contain environment variables, API keys, tokens, and credentials — do not call if the pane may contain sensitive data unless the user has confirmed it is safe. AFTER displaying the output, always ask the user what

• get_config

  Returns the current tmux-mcp configuration: whether tmux is installed, the default session name, and whether the agent is configured to always route shell commands through tmux. Call this at the start of any task to check how the agent should behave. If alwaysUseTmux is true, route all shell commands through send_keys in the configured session instead of direct Bash for the remainder of the task.

• kill_panewrite action

  Kill a tmux pane and terminate its running process. ALWAYS confirm with the user before calling — this is destructive and cannot be undone. Target format: 'session:window.pane'.

• kill_sessionwrite action

  Kill a tmux session and all its windows and panes. ALWAYS confirm with the user before calling — this is destructive and cannot be undone.

• kill_windowwrite action

  Kill a tmux window and all its panes. ALWAYS confirm with the user before calling — this is destructive and cannot be undone. Target format: 'session:window'.

• list_panes

  List panes in a tmux target. Pass a session name ('work') or session:window ('work:0'). When only a session name is passed, lists all panes across all windows in that session. Returns pane index, size, active status, and running command. If there is only one pane, auto-select it without asking. If multiple, present them as choices and ask the user which pane to use.

• list_sessions

  List all active tmux sessions. Returns session name, window count, creation time, and attached status. WHEN TO CALL: Call this immediately whenever the user mentions tmux, asks to attach a session, wants to see terminal output, check logs, run a command in a pane, or interact with any running process. Do not answer from memory — always call this tool first to get live state. WORKFLOW: After gettin

• list_windows

  List all windows in a tmux session. Returns window index, name, pane count, and active status. If there is only one window, auto-select it without asking. If multiple, ask the user which window to use.

• new_sessionwrite action

  Create a new detached tmux session. Before calling, use list_sessions to check whether a session with the requested name already exists.

• new_windowwrite action

  Create a new window in an existing tmux session.

• rename_session

  Rename an existing tmux session.

• rename_window

  Rename a window in a tmux session. Target format: 'session:window'.

• send_keyswrite action

  Send keys or a command to a tmux pane, then capture its output. Target format: 'session:window.pane'. Use enter=false for raw tmux key sequences like 'C-c', 'Escape', or arrow keys — these are not shell commands and must not have Enter appended. Use enter=true (default) for shell commands. Set wait_ms higher for long-running commands; 0 captures immediately before output appears. WARNING: this exe

• split_pane

  Split a tmux pane horizontally or vertically. 'horizontal' = left/right panes side by side. 'vertical' = top/bottom panes stacked. Target format: 'session:window.pane' or 'session:window'.

• Code scan3 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 145 days ago8/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

82/100

higher than 63% of 48,255 servers

Tools

14

the typical server has 7

Tools that change things

43%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

1

more than 65% of 28,688 servers

tmux-mcp: common questions

Is tmux-mcp server safe?

Mostly: it is graded B (82/100). Read the tmux-mcp safety report

How do I install tmux-mcp?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does tmux-mcp need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is tmux-mcp maintained?

The last commit was 182 days ago (2026-05-05). The latest release is v0.3.3.

What can I use instead of tmux-mcp?

Servers from other publishers that do the same job: Ouroboros MCP server.

How does tmux-mcp compare with other MCP servers?

safety score 82/100 (higher than 63% of 48,255 servers); tools 14 (the typical server has 7); tools that change things 43% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.