Skip to main content
Glama
rauls-kjarners

claude-to-agy

by rauls-kjarners
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to claude-to-agy

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

    • antigravity-mcp

      k12club
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets Claude Code call the Google Antigravity CLI (agy) headlessly for a second opinion from a different model family, or to have agy read project files on Claude's behalf so large files never enter Claude's context window.
      18 npm
      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

    • claude-agy-mcp

      PyModel
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets Claude Code delegate heavy tasks (file analysis, deep search, web lookups, adversarial review, and general delegation) to the Antigravity CLI (agy), with model routing, session continuity, timeout controls, and quota-aware failover.
      9
      1,073 npm
      2
      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
      451 PyPI
      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

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no risk of confusion between tools. The single tool's purpose is clearly described, so an agent can easily identify what it does.

    Naming Consistency5/5

    The tool name follows a clear verb_noun pattern ('delegate_to_agy'), consistent with common conventions. With only one tool, naming consistency is inherent.

    Tool Count3/5

    One tool is sparse for a typical MCP server. While the server serves a narrow purpose (delegation to AGY), the single tool may feel insufficient for complex workflows, but it is not excessively heavy.

    Completeness3/5

    The server covers its stated purpose of delegation, but lacks additional tools for managing delegations (e.g., status checks, result retrieval, error handling). There are minor gaps that could affect agent reliability.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources