Skip to main content
Glama
k8ika0s

mcp-tmux

by k8ika0s
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to mcp-tmux

No user-submitted related servers found.

    Related Servers

    • pty-mcp

      raychao-oao
      A
      license
      A
      quality
      B
      maintenance
      Interactive PTY sessions for AI agents — local shells, SSH with persistent sessions (ai-tmux daemon for attach/detach), and serial ports. Single Go binary, no tmux dependency.
      16
      16
      MIT

    • mcp-tmux

      laszlopere
      A
      license
      B
      quality
      C
      maintenance
      A comprehensive MCP server for driving tmux sessions, windows, panes, sending keystrokes, and reading pane output locally or over SSH, enabling real-time collaborative pairing with AI.
      71
      3
      MIT

    • Persistent Shell MCP

      TNTisdial
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to execute shell commands and manage long-running processes within persistent tmux sessions across isolated workspaces. It features a dual-window architecture to separate raw command execution from interactive terminal output.
      8
      8 npm
      1
      MIT

    • Post-Exploitation tmux MCP

      RaghavanSV
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes tmux features to AI agents for managing sessions, windows, and panes with built-in command execution. It includes comprehensive guardrails to prevent destructive system operations, file deletions, and unauthorized network changes.
      -

    • tmux-mcp

      WENLIXIAO-CS
      A
      license
      A
      quality
      D
      maintenance
      Allows AI assistants to create, manage, and interact with tmux sessions, windows, and panes programmatically.
      19
      MIT
    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

    B3.3/5.0

    Scored across 40 tools

    Disambiguation2/5

    Many tools have overlapping purposes, such as tmux_state vs tmux_readonly_state, tmux_capture_pane vs tmux_context_history, and tmux_tail_pane vs tmux_tail_task. Descriptions help somewhat, but an agent could easily misselect among capture, state, and layout variants.

    Naming Consistency4/5

    All tools consistently use the tmux_ prefix and lowercase snake_case, with most following a verb_noun pattern (list_sessions, send_keys, kill_pane). However, a few are noun phrases or less conventional (tmux_state, tmux_server_info, tmux_context_history), creating minor inconsistency.

    Tool Count2/5

    40 tools is excessive for a tmux wrapper; many are near-duplicates or variations (e.g., capture vs state, layout vs profile, tail vs wait). The surface could be reduced to roughly 15-20 distinct tools without losing core functionality.

    Completeness5/5

    The tool set thoroughly covers tmux lifecycle (sessions, windows, panes), inspection, capture, layout management, and task-based polling. The inclusion of tmux_command as a generic escape hatch ensures any missing subcommand can still be executed, leaving no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources