execute_commandLABSCO SUMMARY
The terminal remembers what you did.
A dev server started in one turn is still running in the next, and you can type into it. That is the whole difference from tools that fire a command and lose the process.
What it is
An MCP server that runs commands inside tmux sessions rather than one-shot subprocesses. Each workspace has two windows — exec for commands and ui for output a person is meant to watch — and the session persists after the client closes.
What you get
- Commands executed in a named workspace, with their full output returned
- Long-running and interactive processes started in either window
- Input sent to a process already running, such as a REPL
- Current terminal output captured at any moment
- A running process stopped without tearing down its workspace
- Workspaces created, listed and destroyed, isolated from one another
Requirements
Node.js 18.0.0 or higher and tmux installed on the machine. It runs arbitrary shell commands there and its author labels it experimental, so give it an isolated environment rather than a machine holding real data.
Setup effort
One command — npm install -g tmux-mcp-server
USE CASES
01
Keeping a dev server up across turns
Start it in a workspace and read its output later instead of relaunching each time.
02
Working inside a Python REPL
Start the interpreter in the ui window and send it lines as you go.
03
Running a quick command and reading all of it
Short commands return their full output from the exec window.
04
Keeping two projects from stepping on each other
Give each one its own workspace, created and destroyed independently.
05
Stopping something that has gone wrong
Kill the process and leave the workspace and its scrollback intact.
8 tools
Listed in project docs. Your client may show a different list.
start_processget_outputsend_inputstop_processcreate_workspacedestroy_workspacelist_workspacesBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- Node.js 18.0.0 or higher
- tmux installed on your system
- tmux-mcp-server on PATH
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"tmux-shell": {
"command": "tmux-mcp-server"
}
}
}npm
TERMINAL
npm install -g tmux-mcp-server
