t-pane MCP Server

t-pane MCP Server is an MCP server that connects Claude to tmux sessions, enabling developers to execute terminal commands and manage shell panes directly within their existing command-line environment. Developed for engineers, systems administrators, and software creators who operate inside terminal multiplexers, the server establishes a shared terminal interface between the language model and the user. It organizes work dynamically by provisioning dedicated tmux panes based on project working directories, ensuring distinct tasks do not collide. Rather than relying on simple subshells, t-pane executes commands directly in persistent panes, tracking inputs and returns with unique boundary markers to extract clean output regardless of buffer size. It actively detects interactive prompts, such as password requests or confirmation dialogs, allowing users to step into the pane to complete authentication without breaking the automated flow. Additionally, t-pane records command histories and execution metrics in localized project directories, sends keystrokes, and provisions background panes for extended tasks. This structure keeps terminal operations inspectable, persistent, and synchronized across local sessions.

Category: Cloud & Infrastructure

Tags: automation, cli, shell, terminal, tmux

Visit t-pane MCP Server

How to install and configure t-pane MCP Server

1. Ensure tmux is installed on your PATH and Node.js 18+ is available on your machine. 2. Navigate to your local clone of the repository and build the project: bash npm install npm run build 3. Add the server to your Claude configuration file (such as ~/Library/Application Support/Claude/config.json): json { "mcpServers": { "t-pane": { "command": "node", "args": ["/path/to/t-pane/dist/index.js"] } } } Replace /path/to/t-pane/dist/index.js with the absolute path to your built file. 4. Start an active tmux session by running tmux new-session in your terminal. 5. Restart Claude to register the new server tools.

What you can do with t-pane MCP Server

• Executing terminal commands in project-specific tmux panes and capturing full standard output without truncation. - Detecting interactive terminal prompts such as credentials or confirmation dialogs so users can manually finish input. - Sending pre-filled command text to existing tmux panes for human inspection before manual execution. - Managing multiple directory-aware tmux panes to isolate command executions across different projects without workspace collisions. - Reading and modifying project files through tmux panes while maintaining terminal visibility and user interaction.

Key facts

• https://github.com/cni-locates-rumen/t-pane
• Cloud & Infrastructure, Developer Tools & Code Intelligence
• automation, cli, shell, terminal, tmux

Part of MCP Servers

What is t-pane MCP Server?

t-pane MCP Server is an integration that connects Claude to tmux terminal sessions. It enables the assistant to create panes, execute shell commands, retrieve output, detect interactive user prompts, and manage project workflows within an active terminal multiplexer environment.

Which requirements are needed to run t-pane MCP Server?

You need Node.js version 18 or later and tmux installed on your system path. In addition, you must be operating inside an active tmux session for the server to successfully spawn, identify, and manage your terminal panes.

How does t-pane handle commands requiring passwords or confirmations?

The server monitors command execution for interactive prompts like passwords or confirmation inquiries. When detected, it pre-fills the command in the pane and notifies Claude, allowing you to switch into the tmux pane to complete input manually.

Which MCP clients work with t-pane MCP Server?

t-pane MCP Server works with Claude Desktop and any Model Context Protocol client capable of launching local Node.js processes. To function properly, your client must operate on a system where an active tmux multiplexer session is running and accessible.

Where does t-pane store command execution logs?

Commands, outputs, durations, and exit codes are automatically logged to a local directory named .t-pane/logs/ within your project folder, or to a fallback directory in your home directory if the workspace is not writable.