Skip to main content
Glama
liqiangcc

agent-runtime-mcp

by liqiangcc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to agent-runtime-mcp

No user-submitted related servers found.

    Related Servers

    • kore

      Tiiiktak
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes interactive Claude Code CLI sessions running inside tmux across one or more machines as MCP tools, enabling agents to list, create, read, and drive those sessions over stdio.
      1
      MIT

    • tmux-bridge-mcp

      RaymondYoshida8270
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents running in separate tmux panes to read each other's output, send tasks and messages across panes, and coordinate multi-agent workflows through standard MCP tool calls. It calls tmux directly with no external dependencies beyond tmux itself.
      42 npm
      MIT

    • termcp

      open-mcp-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to interact with real terminal sessions across local and remote hosts, driving multi-turn interactive programs like TUIs, REPLs, and SSH prompts through MCP.
      62
      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
    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.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool targets a distinct action: listing, inspecting, reading, writing, controlling, waiting, and health checking are all separable. The only mild ambiguity is between wait_channel_event and read_channel, but the descriptions clearly separate waiting for activity from reading output.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern: get_channel, list_channels, read_channel, send_control, write_text. The exception is health, which breaks the pattern by being a bare noun rather than something like get_health or check_health.

    Tool Count5/5

    Seven tools is a well-scoped size for a terminal-channel runtime. Each tool covers a meaningful operation without redundancy or bloat.

    Completeness4/5

    The surface covers the core interaction lifecycle for existing channels: inspect, list, read, write, control, and wait. Channel creation/teardown is not exposed, but that may intentionally live outside this server's scope, so it is a minor rather than critical gap.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources