The Tmux MCP Server enables AI assistants to seamlessly control and interact with tmux terminal sessions through API calls.
Session Management: List, search, create, and kill tmux sessions by name or ID.
Window Management: List windows within sessions, create new windows with custom names, and kill existing windows.
Pane Operations: List panes within windows, capture pane content with configurable line count and optional color preservation, split panes horizontally or vertically with customizable sizes, and kill panes.
Command Execution: Run commands in specific panes and retrieve results, with support for interactive applications using raw mode.
Provides tools for listing, navigating, and interacting with tmux sessions, windows and panes. Enables capturing terminal content, executing commands in panes, and creating new tmux sessions and windows.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Tmux MCP Server show me what's running in my tmux sessions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
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!
Related MCP server: TmuxControlLib MCP Server
Node.js
tmux installed and running
Add this MCP server to your Claude Desktop configuration:
"mcpServers": {
"tmux": {
"command": "npx",
"args": ["-y", "tmux-mcp"]
}
}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.
tmux://sessions - List all tmux sessions
tmux://pane/{paneId} - View content of a specific tmux pane
tmux://command/{commandId}/result - Results from executed commands
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
Capture content from a tmux pane with configurable lines count and optional color preservation
Inputs: paneId (required), lines, colors.
Create a new tmux session
Inputs: name (required).
Create a new window in a tmux session
Inputs: sessionId (required), name (required).
Execute a command in a tmux pane and get results. For interactive applications (REPLs, editors), use rawMode=true. IMPORTANT: When rawMode=false (default), avoid heredoc syntax (cat << EOF) and other multi-line constructs as they conflict with command wrapping. For file writing, prefer: printf 'content\n' > file, echo statements, or write to temp files instead
Inputs: paneId (required), command (required), rawMode, noEnter.
Find a tmux session by name
Inputs: name (required).
Get the result of an executed command
Inputs: commandId (required).
Kill a tmux pane by ID
Inputs: paneId (required).
Kill a tmux session by ID
Inputs: sessionId (required).
Kill a tmux window by ID
Inputs: windowId (required).
List panes in a tmux window
Inputs: windowId (required).
List all active tmux sessions
Inputs: no named parameters.
List windows in a tmux session
Inputs: sessionId (required).
Split a tmux pane horizontally or vertically
Inputs: paneId (required), direction, size.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 13 tools
Every tool has a clearly distinct purpose targeting specific tmux resources and actions. For example, create-session, create-window, and split-pane handle different creation tasks, while kill-session, kill-window, and kill-pane handle distinct termination operations. There is no overlap that would cause confusion in tool selection.
All tool names follow a consistent verb-noun pattern with hyphen separation (e.g., create-session, list-panes, kill-window). This uniform naming convention makes the tool set predictable and easy to understand, with no deviations or mixed styles.
With 13 tools, this server is well-scoped for managing tmux sessions, windows, panes, and commands. Each tool serves a specific function in the domain, such as listing, creating, killing, and executing, without being overly sparse or bloated.
The tool set provides complete CRUD/lifecycle coverage for tmux management, including creation (create-session, create-window, split-pane), reading (list-sessions, list-windows, list-panes, find-session, capture-pane), updating (execute-command for command execution), and deletion (kill-session, kill-window, kill-pane). There are no obvious gaps that would hinder agent workflows.
Use your Mac, Windows or Linux computer from ChatGPT, Claude or Codex: files, commands, documents.
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Connect ChatGPT, Claude, Cursor or VS Code to your Windows PC: files, terminal, browser, apps.
