Skip to main content
Glama
JamesZor

Antigravity MCP Server

by JamesZor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Antigravity MCP Server

No user-submitted related servers found.

    Related Servers

    • agy-bridge

      sshahzaiib
      A
      license
      A
      quality
      B
      maintenance
      MCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — purpose-built tools, model routing with fallback, session continuity, and output truncation to save Claude's context and tokens.
      6
      111 npm
      51
      MIT

    • agy-mcp

      Boulea7
      A
      license
      A
      quality
      D
      maintenance
      Wraps Google Antigravity CLI into 11 typed MCP tools, enabling any MCP client to invoke agy for code review, prototyping, execution, and long-running tasks.
      11
      23
      MIT

    • clagy

      mateo-cuello
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that bridges Claude Code to Google Antigravity's CLI, enabling Claude to orchestrate Gemini workers in parallel for reading, writing, verifying, and autonomous tasks. It provides tools for single dispatch, parallel fan-out, background jobs, and handles permission, cwd, and shell pitfalls.
      2
      MIT

    • agy-mcp

      Kaikei-e
      A
      license
      A
      quality
      C
      maintenance
      Lets MCP clients delegate tasks to the Google Antigravity CLI, including starting and continuing conversations and listing models, while returning structured results over stdio.
      3
      24 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between delegate_to_antigravity and start_background_job (both run agy tasks), and between check_job_status and research_status (both poll for status). However, descriptions differentiate them well and the contexts are separate.

    Naming Consistency4/5

    Tools follow a consistent snake_case verb_noun pattern (e.g., check_job_status, collect_digests, propose_design_questions). Minor inconsistencies: auto_git_commit uses a prefix, and some verbs are compound (cross_model_review). Overall, the pattern is clear and predictable.

    Tool Count5/5

    With 13 tools, the server covers a broad domain (git, research, design, code review, background jobs) without being excessive. Each tool earns its place, and the count is appropriate for the advertised capabilities.

    Completeness5/5

    The tool surface covers the full lifecycle of research and design pipelines: question proposal, fanout, status polling, collecting digests, and drafting documents. Additionally, git operations, code indexing, and cross-model review are included. No obvious gaps for the intended use case.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources