claude-tmux
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@claude-tmux spawn session 'task1' in ~/project with prompt 'implement feature'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
claude-tmux
MCP server for orchestrating multiple Claude Code instances via tmux.
Installation
Add to your Claude Code MCP settings:
{
"mcpServers": {
"claude-tmux": {
"command": "npx",
"args": ["-y", "claude-tmux"]
}
}
}Requirements
tmux must be installed
Claude Code CLI must be installed
Related MCP server: cmuxlayer
Tools
spawn
Launch a new Claude Code instance in a tmux session.
spawn(name, prompt, workdir)name: Unique session name (e.g., 'refactor-auth', 'debug-api')prompt: Initial prompt to send to Claudeworkdir: Working directory for Claude to operate in
read
Wait for Claude sessions to finish working and return terminal output.
read(name: "task-name") // single session
read(names: ["a", "b", "c"]) // parallel wait on multiple sessionsFor multiple sessions, use names to wait in parallel - returns all outputs when all complete.
send
Send a follow-up message to a running Claude session.
send("task-name", "do something else")list
List all active Claude tmux sessions.
list()kill
Terminate a Claude tmux session and clean up resources.
kill("task-name")Usage Pattern
spawn(name, prompt, workdir) → start session
read(name) → wait for completion, get output
send(name, text) → steer with follow-up
read(name) → wait again
kill(name) → cleanupFor parallel tasks:
spawn("task-a", ...)
spawn("task-b", ...)
spawn("task-c", ...)
read(names: ["task-a", "task-b", "task-c"]) → wait for allIdle Detection
read detects completion via:
Done indicator - Claude's status line showing
✻ model for XmStability - Output unchanged for 10 seconds (handles sub-minute tasks that don't show the indicator)
Timeout is 15 minutes.
Tips
Verify output shows task completion before killing. Idle agents are fine to leave running.
Attach manually:
tmux attach -t claude-<name>
Available Tools
5 toolskillC
Terminate a session.
Inputs: name (required).
listA
List active sessions.
Inputs: no named parameters.
readA
Wait for Claude sessions to finish working and return their terminal output. Use 'names' for parallel waiting on multiple sessions.
Inputs: name, names.
sendA
Send a message to a running session.
Inputs: name (required), text (required).
spawnB
Start a Claude Code instance in a tmux session.
Inputs: name (required), prompt (required), workdir (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct lifecycle role: spawn creates, send communicates, read collects output, kill terminates, and list enumerates sessions. There is no overlap or ambiguity between their purposes.
All tool names are simple, lowercase imperative verbs following a consistent one-word pattern. This is internally coherent and easy to predict.
Five tools cover the essential operations for managing tmux-based Claude Code sessions without redundancy. The scope is tight and each tool earns its place.
The set covers the complete session lifecycle: create, interact, read output, enumerate, and terminate. There are no obvious gaps for the stated domain of managing Claude Code instances in tmux.
Maintenance
Related MCP Connectors
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server for managing Claude Code conversation sessions1237 npmMIT
- AlicenseAqualityBmaintenanceTerminal multiplexer MCP server for orchestrating parallel AI agents. Manages workspaces, panes, surfaces with send_input/read_screen/spawn_agent/stop_agent tools. Supports Claude Code, Codex, Gemini, Cursor CLI agents with lifecycle management, browser automation, and agent status push via Claude --channels.1030Apache 2.0
- AlicenseAqualityCmaintenanceAn MCP server that gives orchestrator agents fine-grained control over interactive Claude Code sessions running inside tmux, enabling mid-session steering, interruption, and token-efficient result extraction.15MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for programmatic lifecycle management of Claude Code sessions, supporting list, create, read, send, fork, wait, and interrupt operations.6 npm1-