Skip to main content
Glama
Sign In
rhishi99

agy-headless-bridge MCP server

by rhishi99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agy-headless-bridge MCP server

No user-submitted related servers found.

    Related Servers

    • Antigravity MCP Server

      vanh1011
      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

    • antigravity-bridge

      Stemmaker
      A
      license
      B
      quality
      A
      maintenance
      Bridges any MCP client to the official Antigravity agy CLI, letting users delegate tasks, analyze files, search code, look up docs, and request adversarial reviews from their own Antigravity subscription models. Supports dynamic model discovery, multi-turn session follow-up, and async long-running tasks without replacing the client's main model.
      10
      1
      MIT

    • agy-mcp

      Boulea7
      A
      license
      A
      quality
      A
      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
      56 PyPI
      26
      MIT

    • agymcp

      leologoli
      F
      license
      Not graded
      quality
      C
      maintenance
      Wraps the Antigravity CLI (agy) as an MCP server, enabling Claude Code and other MCP clients to execute AI tasks and manage conversations via the agy command.
      -
    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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation3/5

    agy_ask and agy_research both send a prompt to the same Antigravity CLI and return a response, so the boundary is blurred: a user could fulfill research needs by calling agy_ask with a 'research this' prompt. The description hints at a depth/intent difference, but nothing structural distinguishes the two tools (no separate parameters, output shapes, or guarantees).

    Naming Consistency5/5

    Both tools use the same agy_ prefix with a single lowercase snake_case verb (ask, research), forming a clean, predictable pattern. There is no mixing of conventions or verb styles.

    Tool Count3/5

    Two tools is thin for a bridge server, and one of them (agy_research) appears to be a thin wrapper around the other, so the surface feels under-scoped rather than deliberately minimal. It is not extreme, but there is little room for distinct capability.

    Completeness3/5

    The server covers one-shot prompt delegation but lacks any session/multi-turn continuation, file or workspace context parameters, or status/cancel operations that a CLI bridge typically needs. Core workflow (ask something and get an answer) works, but agents will hit dead ends for stateful or long-running tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources