Skip to main content
Glama

Related Servers

Alternatives to agent-shuttle-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Agent orchestration system that runs coding-agent sessions (Claude Code, Codex) with policy mediation and exposes tools via MCP.
      -
    • 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
      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
      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
      B
      maintenance
      Enables delegating coding tasks to Claude Code, Codex or OpenCode agents over the Agent Client Protocol, running a prompt to completion in a chosen directory and returning the agent's result. Also supports follow-up messages, background turns, session listing, cancellation, and harness discovery with configurable permission policies.
      6
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts like Claude Code and Codex to spawn, manage, and interact with persistent, reusable Pi coding-agent sessions, supporting task dispatch, status checks, and session lifecycle control.
      3 npm
      -

    TDQS

    B3.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    The three ask_* tools target different agents (generic configured profiles, Antigravity, Codex), and the three get_*_info tools mirror that structure. However, the generic ask_agent/get_agent_info could be confused with the specific ask_antigravity/get_antigravity_info or ask_codex/get_codex_info if those agents are also configured, requiring careful reading of descriptions.

    Naming Consistency5/5

    All tool names follow a clear ask_<target> or get_<target>_info pattern in consistent snake_case. The generic 'agent' target versus specific agent names is a meaningful distinction rather than a naming inconsistency.

    Tool Count5/5

    Six tools is well-scoped for a delegation server, covering ask and info operations for both generic and specific agents without redundancy. Each tool earns its place.

    Completeness3/5

    The core ask and info operations are present, but there is no list_agents tool to discover which profiles are available in BRIDGE_AGENTS_JSON. This is a notable gap for a server centered on configured agents, as users must already know the agent names.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues