Tmux MCP Server

If you want an AI assistant working directly with Tmux MCP, the tmux mcp mcp server is the bridge. MCP Server for interfacing with tmux sessions.

What Tmux MCP does

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.

Key capabilities

• 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

Tools it exposes

Once connected, the assistant can call these 13 tools directly:

• list-sessions — List all active tmux sessions
• find-session — Find a tmux session by name
• list-windows — List windows in a tmux session
• list-panes — List panes in a tmux window
• capture-pane — Capture content from a tmux pane
• create-session — Create a new tmux session
• create-window — Create a new window in a tmux session
• split-pane — Split a tmux pane horizontally or vertically with optional size
• kill-session — Kill a tmux session by ID
• kill-window — Kill a tmux window by ID
• kill-pane — Kill a tmux pane by ID
• execute-command — Execute a command in a tmux pane
• get-command-result — Get the result of an executed command

Installing the tmux mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Requirements

• Node.js - tmux installed and running

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Tmux MCP sits in that group, and the shape of its toolset — list-sessions, find-session, list-windows among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• With 13 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Tmux MCP.
• Maintained by nickgnd.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the tmux mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.