tmux-claude MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spawnB | Spawn a new Claude instance with role and context |
| sendB | Send text/prompt to a Claude instance |
| readC | Read output from a Claude instance |
| listB | List all active Claude instances |
| terminateA | Terminate a Claude instance and optionally its children |
| restartB | Restart a dead instance using --continue flag |
| executeParallelB | Execute multiple tasks in parallel using Specialist instances (Manager only) |
| getParallelStatusB | Get parallel execution status for a Manager |
| distributeWorkB | Distribute tasks across multiple Managers (Executive only) |
| merge_manager_workB | Coordinate merge of manager work back to main branch (Executive only) |
| check_workspace_conflictsC | Analyze potential conflicts in shared workspace |
| sync_manager_branchB | Sync manager branch with latest main branch changes (Manager only) |
| commit_manager_workB | Commit current work with proper git practices (Manager only) |
| get_workspace_statusC | Get comprehensive status of shared workspace |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool targets a distinct operation: workspace management, instance lifecycle, parallel execution, and git operations. Tools like check_workspace_conflicts and get_workspace_status have clear boundaries, and even similar-sounding ones like distributeWork and executeParallel are differentiated by context (scheduling vs. running).
The set uses a mix of snake_case (e.g., check_workspace_conflicts, commit_manager_work) and camelCase (e.g., distributeWork, executeParallel), plus short verbs (list, send, read). While each subgroup is internally consistent, the overall pattern is not uniform, which may cause slight confusion.
14 tools cover the main aspects of instance management and workspace coordination without being excessive. The scope is well-defined, and each tool serves a necessary role in the multi-instance workflow.
The tool surface covers the key lifecycle operations (spawn, terminate, restart, send/read), parallel execution, and basic git workflow (commit, sync, merge). Minor gaps exist (e.g., no explicit tool for listing workspace files or pruning instances), but the core functionality is solid.