Skip to main content
Glama
yinjs

agyenvoy

by yinjs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to agyenvoy

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • 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.
      24 npm
      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.
      25 npm
      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
      53 npm
      7
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: asking the CLI, checking auth status, listing models, and logging in. There is no functional overlap or ambiguity among them.

    Naming Consistency5/5

    All tool names follow a consistent 'agy_verb' pattern (ask, auth_status, list_models, login) using snake_case. The pattern is predictable and easy for an agent to learn.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped to the essential operations of the agy CLI: authentication, model discovery, and making requests. Each tool is necessary and there is no bloat.

    Completeness4/5

    The tool surface covers the core interaction loop: authenticate, check status, list models, and send prompts. Minor gaps exist—e.g., no tool to list ongoing conversations or manage projects directly—but these are partially addressed via parameters in agy_ask, so agents can still function.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources