Skip to main content
Glama
EtanHey

cmuxlayer

by EtanHey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cmuxlayer

No user-submitted related servers found.

    Related Servers

    • hyperpanes-mcp

      Eyalm321
      A
      license
      A
      quality
      C
      maintenance
      MCP server for hyperpanes terminal workspace app, enabling AI agents to compose and launch workspace layouts, inspect and drive terminal panes, stream output, and orchestrate agent hierarchies.
      47
      1
      MIT

    • tmux-bridge

      tguo9004
      A
      license
      Not graded
      quality
      A
      maintenance
      A standalone MCP server that lets AI agents running in separate tmux panes read each other's output, send messages and keystrokes into other panes, and coordinate multi-agent workflows without copy-pasting context. It talks directly to tmux over stdio using standard MCP tool calls such as tmux_read, tmux_message, tmux_keys, and tmux_name.
      36 npm
      MIT

    • tmux-bridge-mcp

      Beatriceh4206
      A
      license
      Not graded
      quality
      A
      maintenance
      A standalone MCP server that lets AI coding agents running in separate tmux panes read each other's output, send messages and keystrokes, and coordinate multi-agent workflows through standard MCP tool calls. It shells out directly to tmux, so no external dependencies beyond tmux itself are required.
      36 npm
      MIT

    • Forge

      ferodrigop
      A
      license
      Not graded
      quality
      D
      maintenance
      Terminal MCP server for AI coding agents with persistent PTY sessions, ring-buffer incremental reads, headless xterm screen capture, multi-agent orchestration, and a real-time web dashboard.
      14 npm
      28
      MIT

    • Onda MCP

      mindfullabai
      A
      license
      A
      quality
      B
      maintenance
      MCP server to control Onda terminal from AI agents, providing tools for splitting panes, running commands, managing tabs and workspaces, and orchestrating multi-agent workflows across multiple windows.
      39
      5 npm
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool has a reasonably distinct purpose: spawn, send, list, close, read, wait, health, report. There is mild overlap between list_agents and list_surfaces (agents live on surfaces) and among the surface-touching tools (spawn_agent, update_surface, close_surface), but descriptions clarify the boundaries.

    Naming Consistency4/5

    Nearly all names are snake_case with a verb_noun or verb_prep pattern (control_health, spawn_agent, list_agents, update_surface, close_surface, list_surfaces, read_screen). Minor deviations are the prepositional forms send_to, wait_for, and report_to_parent, which are still readable and consistent in style.

    Tool Count5/5

    Ten tools is well within the ideal range and each covers a distinct facet of agent/surface orchestration. No redundant or filler tools appear; the set feels tightly scoped to the domain.

    Completeness4/5

    The surface covers the full lifecycle: spawn/resume, list, send, read, wait, update/adopt, close, report, and health. Coverage is strong, with only minor gaps such as no dedicated agent-state update beyond update_surface's adoption path.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources