Tmux Mcp
Let agents list tmux sessions, read pane output, and inject commands for long-running dev servers and tests.
Overview
tmux-mcp is a MCP server for the Build phase that lets agents browse tmux sessions, capture output, and send commands over stdio.
What is this MCP server?
- tmux-mcp v0.3.3 (@fr1sk/tmux-mcp) with stdio MCP transport
- Browse tmux sessions and panes from the agent
- Capture live terminal output for context-aware debugging
- Send commands into running sessions without manual copy-paste
- Version 0.3.3
- npm package @fr1sk/tmux-mcp
- Stdio transport per MCP 2025-12-11 schema
What problem does it solve?
Agents miss context when builds and tests run in detached tmux panes the model cannot see or control.
Who is it for?
Developers who live in tmux and want Claude Code or Cursor to debug long-running processes in place.
Skip if: Windows-only workflows without tmux or teams that forbid agents from sending terminal input.
What do I get? / Deliverables
After install, your agent can inspect tmux panes and run commands in live sessions during dev and ops work.
- Session and pane listing tools for agents
- Captured tmux output fed into agent context
- Command injection into selected tmux panes
Recommended MCP Servers
Journey fit
How it compares
Live tmux control MCP, not a static log-file reader skill.
Common Questions / FAQ
Who is Tmux Mcp for?
Solo builders and power users on Linux or macOS who run dev stacks in tmux and use MCP-enabled coding agents.
When should I use Tmux Mcp?
Use it when servers, tests, or tail processes run in tmux and the agent needs real pane output or to send the next command.
How do I add Tmux Mcp to my agent?
Install @fr1sk/Tmux Mcp, ensure tmux is on PATH, add the stdio server entry in your MCP settings, and grant the agent permission to invoke its session tools.