claude-tmux-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_CLAUDE_DEBUG | No | Set to 'true' for verbose debug logging | false |
| MCP_POLL_INTERVAL_MS | No | How often to poll the pane for output changes | 1500 |
| MCP_STARTUP_DELAY_MS | No | Wait after sending prompt before polling starts | 1000 |
| MCP_STABLE_THRESHOLD_MS | No | Fallback: ms of no change before declaring done | 3000 |
| MCP_CLAUDE_READY_TIMEOUT | No | Max ms to wait for Claude Code to start up | 30000 |
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 |
|---|---|
| claude_codeA | Send a prompt to an interactive Claude Code session running in a tmux terminal. Sessions and Claude Code are started automatically if not already running. The user can attach to the session at any time to watch Claude work: tmux attach -t {session-name} SESSION NAMING: workFolder /Users/you/my-roblox-game → session: claude-my-roblox-game No workFolder → session: claude-code BEHAVIOUR: • If the tmux session doesn't exist it is created automatically. • If Claude Code isn't running in the session it is started automatically. • Only one prompt at a time per session — concurrent calls return a busy error. • Conversation history is fully preserved between calls. • Claude Code has access to all configured MCP tools (Roblox Studio, Godot, Blender, etc.). |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The single tool's purpose is crystal clear.
With only one tool, naming consistency is trivially maintained. The name 'claude_code' accurately reflects its function.
One tool feels thin for a bridge server, but it does encapsulate the core operation. A more complete set might include session management tools.
The tool covers the primary use case of sending prompts and implicitly handles session startup. Minor gaps like explicit session listing or termination exist.