Skip to main content
Glama
funkyfunc

coding-agents-mcp

by funkyfunc

Related Servers

Alternatives to coding-agents-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI coding CLIs (Claude Code, Gemini/Antigravity, Codex, and OpenCode) to collaborate as a coordinated team by routing cross-agent prompts, sharing messages and review tickets, tracking tasks on a shared store, and isolating each agent in its own Git worktree with turn-budget safeguards—all inspectable and steerable from a local web dashboard.
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      Enables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.
      14
      7 npm
      14
      MIT

    TDQS

    C2.7/5.0

    Scored across 16 tools

    Disambiguation2/5

    Several tools are exact legacy aliases (agy_task/agy_diff/agy_sessions/agy_reset/agy_ask duplicate their delegate_* counterparts), and agy_run_task/agy_chat also overlap with delegate_task. The alias tags add clarity, but the surface still exposes multiple names for nearly the same operation.

    Naming Consistency3/5

    The delegate_* tools follow a clean verb_noun pattern and the agy_* prefix gives some unity. However, agy_run_task vs agy_task, the outlier agents_status, and noun-style entries like agy_version and agy_diff make the naming convention inconsistent.

    Tool Count3/5

    16 tools is at the heavy end for this server's scope, and several of those entries are redundant legacy aliases. The true unique tool count is closer to 10, so the set feels inflated rather than lean.

    Completeness4/5

    Core workflows are well covered: task delegation, read-only asks, diff inspection, session management, reset, status, planning, and Antigravity runtime details are all present. Lifecycle controls such as aborting or canceling an in-progress task are the only notable omission.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues