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