Loading connector details…
Loading connector details…
Choose a unique username to continue using AgentHotspot
by jonrad • Workflow & Task Management
A proof-of-concept server for controlling tmux sessions programmatically using the Model Context Protocol.
Automate tmux session management.
Integrate tmux controls within larger workflows.
Experiment with MCP server implementations.
Tmux MCP Server is a demonstration of implementing the Model Context Protocol to allow programmatic control over tmux sessions. It enables users to run arbitrary tmux commands, which can be useful for automating and integrating tmux session controls in various applications. Note that this is a proof-of-concept and should not be used in production environments.
List all tmux sessions with their names, IDs, window count, and status.
List all tmux windows. Optionally filter by session name or ID. Args: session: Session name or ID to filter by. If omitted, lists windows from all sessions.
Send keys or commands to a tmux pane. Args: target: Tmux target (e.g. "session:window.pane", "session:window", "session"). keys: Keys to send. Use special key names like "Enter", "C-c", "Escape", "Tab", "Space", etc. literal: If true, send keys literally (the -l flag) without special key lookup.
Read/capture content from a tmux pane. Args: target: Tmux target (e.g. "session:window.pane"). line_count: Number of lines to capture. If omitted, captures entire visible pane. start_line: Start line for history capture (negative = lines before visible area, e.g. -100).
Create a new tmux session. Args: name: Name for the new session. command: Optional command to run in the initial window. window_name: Optional name for the first window.
Scores are informational only and provided “as is” without warranty. AgentHotspot assumes no liability for actions taken based on these ratings.