Skip to main content
Glama
bgembalczyk

agent-antigravity-mcp

by bgembalczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to agent-antigravity-mcp

No user-submitted related servers found.

    Related Servers

    • gpal

      tobert
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives your IDE or agent access to Google Gemini with autonomous codebase exploration, enabling deep code analysis, architectural reviews, and bug hunting.
      20
      10
      MIT

    • agy-mcp

      Sh3rm
      A
      license
      Not graded
      quality
      F
      maintenance
      This MCP server bridges Claude Code with the Antigravity CLI (agy), allowing Claude to delegate tasks to Google Gemini models via configurable difficulty tiers. It verifies the actual backend model for every call, provides separate tools for safe ask/research vs. shell exec, and supports long-running background jobs.
      11 npm
      MIT

    • Gemini Agent MCP Server

      cybaea
      A
      license
      A
      quality
      C
      maintenance
      An advanced MCP server that provides an agentic interface to Google's Gemini 3.1 models via Vertex AI, combining real-time Google Search, URL analysis, and Python code execution to solve complex multi-step research and data tasks.
      1
      MIT

    • agent-intern

      SinanTufekci
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that bridges Claude Code with Antigravity CLI using a Swarm Agent architecture to optimize local development workflows and minimize LLM token costs. Includes a web UI for monitoring agent workflows.
      24
      22
      MIT
    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

    A3.7/5.0

    Scored across 27 tools

    Disambiguation5/5

    Tools are clearly organized into distinct categories (interactions, triggers, managed agents, environments, helpers) with no overlapping purposes. Even similar tools like create_interaction and continue_interaction are well-differentiated.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern, making them predictable and easy to navigate. Even longer names like build_mcp_server_tool_config adhere to this convention.

    Tool Count4/5

    At 27 tools, the set is extensive but justified given the server's broad scope covering interactions, triggers, agents, environments, and configuration helpers. Each tool serves a clear purpose without redundancy.

    Completeness5/5

    The server provides comprehensive CRUD-like coverage for each domain: interactions (create, continue, submit, get status, cancel, delete, list), triggers (create, list, update status, delete, run, list executions), managed agents, and environments, plus helper tools for building configs.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources