Skip to main content
Glama

Related Servers

Alternatives to throng

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables launching and supervising local Codex and Claude Code agent sessions and one-shot tasks, exposing run, list, stop, and output operations over MCP with session-scoped permissions and sandbox controls.
      5
      4,779 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to delegate prompts to locally configured Codex, Antigravity, OpenCode, and Claude Code agents, fetch live model catalogs and quotas, and maintain stateful multi-turn sessions with selectable tool policies.
      6
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Wraps Claude Code as tools for MCP clients, enabling autonomous coding tasks via a 4-tool lifecycle with session management, async polling, and permission controls.
      4
      59 npm
      20
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact programmatically with Claude Code CLI, managing sessions, streaming outputs, and handling permission requests.
      7
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code and Claude Desktop to delegate coding tasks to any model available in OpenCode while Claude remains the orchestrator, planning work, reviewing diffs, and running tests. Supports synchronous and async delegation, model selection, session continuation, and permission-aware execution.
      MIT

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (list sessions, list harnesses, cancel, wait, run, send). The main overlap is run_thronglet vs send_message, which both start a turn and return identical JSON, though the descriptions clarify new-session vs existing-session intent.

    Naming Consistency4/5

    All six tools use snake_case verb_noun form (list_thronglets, cancel_thronglet, run_thronglet, wait_thronglet, send_message, list_harnesses), which is predictable. Minor inconsistency in pluralization (list_thronglets/harnesses vs singular cancel/run/wait_thronglet) and send_message breaks the 'thronglet' noun pattern.

    Tool Count5/5

    Six tools is well-scoped for a session-orchestration server; each maps to a distinct lifecycle action (run, send, wait, cancel, list sessions, list harnesses). No filler or redundant tools.

    Completeness4/5

    Covers the core lifecycle: discover harnesses, run a session, message it, wait on it, cancel it, and list sessions. Minor gap: no explicit way to fully terminate/delete a session or fetch a single session by id (only cancel the current turn, and list all).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues