Skip to main content
Glama

Related Servers

Alternatives to agy-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Lets MCP clients such as Claude Code, Claude Desktop, Cursor, or Codex hand tasks to the Antigravity CLI (agy) so the work runs on the user's Antigravity plan instead of the client's. Exposes tools for delegated coding tasks and reviews, web search with sources, image/PDF analysis, shell command generation or execution, brainstorming, and model/quota checks.
      7
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients such as Claude Code and Cursor to delegate long multi-step coding tasks to Google Antigravity CLI, generate read-only plans and code reviews, digest large codebases, and manage background sessions in isolated git worktrees.
      15
      43 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible coding agents to run the local Antigravity CLI as a coding agent, manage conversation context and common options, and inspect usage, quota, models, version, help, and read-only slash commands.
      26 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 7 tools

    Disambiguation4/5

    The core trio (agy_ask, agy_ask_new, agy_resume) is clearly delineated by the persistent-vs-fresh-vs-resume distinction, and agy_stop/agy_models are unmistakable. The only soft overlap is agy_status vs agy_conversations, since status also reports live conversations, but the descriptions make the difference (diagnostics vs enumeration) reasonably clear.

    Naming Consistency4/5

    All names share a uniform `agy_` prefix and snake_case, which makes the set highly predictable. The only minor wrinkle is the mixed verb/noun style (agy_ask/agy_resume/agy_stop vs agy_models/agy_conversations/agy_status), though that maps naturally to action vs listing tools.

    Tool Count5/5

    Seven tools is a tight, well-scoped surface for a conversation-lifecycle wrapper around a single external agent. Each tool covers a distinct lifecycle step (start, fresh start, resume, list, stop, introspect models, introspect status) with no filler.

    Completeness4/5

    The conversation lifecycle is essentially covered: create, create-fresh, resume, list, stop, plus introspection of models and status. Gaps are minor but real: there is no way to pass a model selection into agy_ask despite agy_models existing, and no way to inspect or delete conversation history/messages.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues