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

    • ddx-term-mcp

      Dudoxx
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to execute commands in a shared tmux session that is simultaneously visible to a human via a web-based terminal UI.
      1
      MIT

    • tmux-shell

      ketema
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to read tmux pane content on-demand, providing context-aware assistance during interactive terminal sessions.
      2
      MIT

    • Agent Collaboration MCP Server

      nishimoto265
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to orchestrate a team of sub-agents through tmux sessions for complex task delegation and parallel implementation. It provides tools for launching agents, monitoring their real-time status, and managing communication between them.
      6
      11 npm
      26
      MIT
    • crosstalk by epode-studio

      crosstalkofficial

      epode-studio
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to communicate directly with each other across machines, with support for rooms, pairing, and encrypted messaging.
      5 npm
      3
      MIT

    • wezterm-agent-mcp

      multiagentcognition
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables orchestration of multiple AI coding agents (Claude Code, Gemini CLI, etc.) in isolated Wezterm panes, allowing one agent to spawn, monitor, and communicate with others across projects.
      6 npm
      1
      -
    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

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources