Skip to main content
Glama

Related Servers

Alternatives to agent-intern

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that bridges CLI coding agents like Claude Code, Codex, opencode, and Antigravity into any MCP client, enabling synchronous and asynchronous task execution, follow-up input, and a structured code review tool.
      34 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.
      47
      76 npm
      2
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server and HTTP gateway that dispatches coding tasks to Claude Code, Codex, and Antigravity CLI sessions, keeps track of those sessions, and optionally runs an implement → review → verify loop against a real repository.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that bridges Claude with KiloCode, enabling Claude to act as architect and delegate coding tasks to Kilo's fast CLI agent while monitoring progress and reviewing results.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that lets Claude Code call the Google Antigravity CLI (agy) headlessly for a second opinion from a different model family, or to have agy read project files on Claude's behalf so large files never enter Claude's context window.
      26 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 32 tools

    Disambiguation3/5

    The ask/continue/status split per backend is clear, and the swarm/image tools have distinct roles, but nine near-identical `*_ask` tools (grok, codex, copilot, cursor, claude, kimi, opencode, muse, antigravity) differ only by which CLI/login backs them, so an agent has to parse prose rather than tool names to pick correctly. `agent_swarm` vs `preset_swarm` vs `swarm_presets` are also close enough to invite misselection on first read.

    Naming Consistency4/5

    27 of 32 tools follow a strict `<backend>_<action>` snake_case pattern with a uniform ask/continue/status triple. The outliers (`swarm_presets`, `agent_swarm`, `preset_swarm`, `antigravity_image_swarm`) break the verb-last convention but remain readable.

    Tool Count3/5

    32 tools is heavy, though the bulk is combinatorial (9 backends x 3 lifecycle operations) rather than redundant. Each tool is genuinely distinct, but the surface is larger than an agent can comfortably hold in mind and could be collapsed (e.g. one `ask` with a backend parameter).

    Completeness4/5

    Coverage is strong: every backend gets status/ask/continue, plus image generation, image fan-out, ad-hoc swarms, preset panels, and preset discovery. Gaps are minor but real — no session listing/cleanup, no way to cancel or interrupt a running swarm, and no tool to create or validate custom swarm presets (only file edits on disk).

    Maintenance

    ActivityActive
    ResponsivenessOutdated data