Skip to main content
Glama
trolleydodger1988

tmux-mcp

by trolleydodger1988
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TMUXNoName of the persistent tmux sessionlocal_agent_workspace
UV_PROJECT_ENVIRONMENTNoVenv location (keep on ext4 under WSL).venv in project

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
execute_commandA

Dispatch a raw shell command string into the persistent background workspace pane (FR-02). The text is sent literally, then a carriage return (C-m) is appended to ensure statement completion.

By default output is NOT returned — poll read_terminal_buffer to observe
results. Pass wait_s > 0 to sleep that many seconds (capped at 30.0)
after dispatch and get the trailing buffer back in the same call —
ideal for quick commands. Long jobs should still dispatch, then poll.
read_terminal_bufferA

Capture trailing scrollback from the active tmux pane (FR-03).

Hard-wrapped rows are joined and trailing blank viewport padding is
trimmed before the payload is returned.

Args:
    lines: Number of trailing scrollback lines to capture (default 100,
        max 20000).
send_control_signalA

Issue a control signal keystroke to the persistent pane (FR-04), e.g. SIGINT (Ctrl+C) to break out of a blocking process without killing the harness. Supported: SIGINT, SIGTSTP, SIGQUIT, EOF.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool addresses a distinct action: sending commands, reading output, and sending control signals. There is no overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (execute_command, read_terminal_buffer, send_control_signal), with no deviations.

Tool Count5/5

Three tools cover the essential interactions with a tmux pane (write, read, signal). This is well-scoped for a minimal but functional MCP server.

Completeness4/5

The tools cover the core workflow of dispatching commands and retrieving output. Missing operations like pane management or clearing the buffer are minor gaps given the focused scope.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources