howardpen9/tmux-bridge-mcp
Standalone MCP server for cross-pane AI agent communication via tmux. Lets Claude Code, Gemini CLI, Codex, and Kimi CLI talk to each other through tmux panes.
Platform-specific configuration:
{
"mcpServers": {
"tmux-bridge-mcp": {
"command": "npx",
"args": [
"-y",
"tmux-bridge-mcp"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
English | 简体中文
A standalone MCP server that lets AI agents (Claude Code, Gemini CLI, Codex, Kimi CLI) communicate with each other through tmux panes. It talks directly to tmux -- no external dependencies beyond tmux itself.
tmux is a terminal multiplexer -- it lets you split one terminal window into multiple panes, each running its own process independently. Think of it as "tabs on steroids" for your terminal.
+-------------------------------+
| Pane 1 | Pane 2 |
| Claude Code | Codex |
| writing code | reviewing |
| | |
+---------------+---------------+
| Pane 3 | Pane 4 |
| Gemini CLI | tail -f logs |
| researching | monitoring |
+-------------------------------+Each pane is a full terminal. You can have Claude Code running in one, Codex in another, Gemini in a third -- all visible at the same time, all on the same machine.
The problem: these panes can't talk to each other. An agent in Pane 1 has no idea what's happening in Pane 2.
tmux-bridge fixes this. It gives every agent the ability to read, type, and send messages into any other pane.
Once installed, your AI agents can:
| Action | How | Example | |--------|-----|---------| | See what another agent is doing | tmux_read | Read the last 20 lines of Codex's pane | | Send a task to another agent | tmux_message + tmux_keys | Tell Claude to review a file | | Coordinate multi-agent workflows | Chain tool calls | Gemini researches -> Claude implements -> Codex reviews | | Monitor processes | tmux_read on a shell pane | Watch build logs, test output, server status |
Loading reviews...