Tmux MCP Server

npx -y tmux-mcp

{
  "mcpServers": {
    "tmux-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tmux-mcp"
      ]
    }
  }
}

The point of going through tmux instead of spawning a subprocess is that the session outlives the conversation and stays visible to the human sitting in front of it. Sessions, windows and panes are addressable, capture-pane returns whatever a long-running process has printed so far without interrupting it, and the server can create sessions, split panes with a size, and kill any of the three. Panes are also published as MCP resources under tmux:// URIs, so a client can watch one without a tool call. Command execution needs to know which shell is in use to read an exit status correctly — it assumes bash unless told otherwise. Anything the assistant runs here runs unrestricted.