tmux-mcp

MCP.Pizza Chef: nickgnd

Aimed squarely at people who live in a terminal. It reads the contents of your tmux sessions, windows, and panes, so an assistant can see what a command printed, and it can create sessions, split panes, close them, and run commands of its own. You need tmux and Node already installed, then two lines pasted into your assistant's settings. Worth knowing first: the project has had no new commits since February 2026, and the author marks command execution as use-at-your-own-risk.

Coding
Other

Use This MCP server To

Read what my long-running build printed in another window Ask why a command failed without copying its output Set up a new session with the panes already split List every terminal session I currently have open Run a command and get the result back in chat

README

Tmux MCP Server

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!


youtube video

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 sessions
  • tmux://pane/{paneId} - View content of a specific tmux pane
  • tmux://command/{commandId}/result - Results from executed commands

Available Tools

  • 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

tmux-mcp FAQ

Is this still being maintained?
It still works, but there have been no new commits since February 2026. The author has not named a replacement, so treat it as finished rather than growing.
Do I need tmux already?
Yes. tmux is a separate terminal tool you install yourself, and this does nothing without it. Node also has to be installed.
Which apps does it work in?
The instructions cover Claude Desktop, and any other MCP app that accepts the same style of configuration will work.
Do I need a key or an account?
No. It works entirely against terminal sessions on your own machine.
Can I use this to check on a script that is still running?
Yes — it can capture whatever a pane is showing right now and hand that back to the assistant.
Is it safe to let it run commands?
The author flags command execution as use-at-your-own-risk. Anything it runs carries your own permissions, so watch what you approve.
How hard is the setup?
Easy if you already use tmux — paste a two-line block into your assistant's settings, and optionally name the shell you use.