Skip to main content
Glama
howardpen9

tmux-bridge-mcp

by howardpen9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tmux-bridge-mcp

No user-submitted related servers found.

    Related Servers

    • tmux-bridge-mcp

      dblanchard5035
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents running in separate tmux panes to read each other's output, send messages, and inject keystrokes, so multiple agents can coordinate workflows, hand off tasks, and review each other's work without manual copy-pasting.
      42 npm
      MIT

    • tmux-bridge-mcp

      jeong0383
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI agents to read, type, and send messages into other tmux panes, allowing them to coordinate multi-agent workflows, monitor processes, and exchange context without manual copy-pasting.
      42 npm
      MIT

    • tmux-bridge-mcp

      BuiMoore
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents running in separate tmux panes to read, type into, and message each other through standard MCP tool calls, coordinating cross-pane workflows without custom frameworks or protocols.
      42 npm
      MIT

    • tmux-bridge-mcp

      virginienair86
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents running in separate tmux panes to see and talk to one another by reading pane output, sending keystrokes, and relaying messages through standard MCP tool calls. This lets users coordinate multi-agent workflows, hand tasks between agents, and monitor shell processes without manually copy-pasting context.
      42 npm
      MIT

    • tmux-bridge-mcp

      egorov01543
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents running in separate tmux panes to read each other's output, send messages and keystrokes, and coordinate multi-agent workflows through standard MCP tool calls. It lets existing MCP-compatible agents communicate cross-pane without requiring a multi-agent framework or extra infrastructure beyond tmux.
      42 npm
      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

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct action on tmux panes: labeling, resolving, listing, reading, typing, sending keys, messaging, diagnostics. No two tools overlap in purpose, and the read guard enforces a clear workflow without ambiguity.

    Naming Consistency5/5

    All tools follow the 'tmux_' prefix with a concise verb: tmux_name, tmux_resolve, tmux_id, tmux_doctor, tmux_list, tmux_read, tmux_type, tmux_message, tmux_keys. The pattern is uniform and predictable.

    Tool Count5/5

    With 9 tools, the server covers all core interactions with tmux panes (label, identify, list, read, type, key, message) plus diagnostics. This is a well-scoped set—neither too few nor too many.

    Completeness4/5

    The tools cover the essential CRUD-like operations for tmux panes: reading, writing (type/keys), labeling, and listing. Missing would be creating new panes or advanced flush/wait operations, but these are outside the server's stated scope as a bridge.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources