agy-mcp

Personal tool, published as-is. This is not a product: it is not on npm, it is not maintained for anyone else, and there is no support. The repository is archived — read it, copy from it, fork it freely, but do not expect issues or pull requests to be answered. If you want something maintained, agy-bridge is an actively developed alternative with a broader tool surface.

An MCP stdio server that makes the Antigravity CLI (agy) a first-class tool inside Claude Code — and verifies, on every single call, which backend model actually answered.

If you pay for both Claude Code and Google AI Pro, this lets you spend the cheaper subscription on the cheaper work without leaving Claude Code. Claude stays the driver; agy becomes a tool it can hand a task to.

You  →  Claude Code  →  agy_ask(tier: "trivial")  →  agy  →  Gemini Flash
                                                       ↓
                                   [verification] OK — served by "Gemini 3.6 Flash (Low)"

Why not an LLM gateway or proxy

The common way to mix providers is to point Claude Code's Anthropic API traffic at a proxy that translates it to another vendor's API. That means intercepting requests, and often reusing credentials issued to a different client.

This server does none of that. There is no proxy, no API translation, no credential relay, and nothing is re-signed or intercepted. Claude Code talks to Anthropic on your Anthropic account. agy talks to Google on your Google account, through Google's own official CLI, exactly as if you had typed the command yourself. All this server does is let Claude spawn that CLI as a subprocess and read its output.

Check your own subscriptions' terms and decide for yourself whether this fits them. This README makes no legal claim on your behalf.

Related MCP server: agyforclaude

What you get over calling agy through Bash

• Backend verification on every call. agy's --model flag is not always honoured, and the model's own self-report will not tell you. Every result is prefixed with a [verification] line naming the model that really served it, parsed out of agy's own log.

• Known-broken model ids are refused by default, rather than silently answering from the wrong model.

• New routing bugs are detected on their own — see Model routing verification.

• Difficulty tiers, not model ids. Claude picks trivial / standard / hard / reasoning, and the server resolves that against the live model list.

• No shell permission prompt per call, and no risk of the command being reshaped by a shell wrapper.

• Long runs do not die on the tool timeout. A deep research call hands back a job_id; the run continues in the background and Claude collects it with agy_result.

• The dangerous capability is a separate tool (agy_exec), so the rest can be allowlisted safely. See Security model.

Requirements

• Node.js ≥ 18 (zero dependencies)

• The Google Antigravity CLI (agy) installed, on PATH, and signed in

• Claude Code

Built and tested against agy 1.1.10.

Install

Not published to npm, and there are no plans to. Clone it and point Claude Code at the script — there is nothing to build, and no dependencies to install.

git clone https://github.com/Sh3rm/agy-mcp.git
cd agy-mcp
npm test          # optional; needs neither agy nor network

Register with Claude Code

MCP servers can be registered at three scopes. Pick the one that matches how you want to use it. Use the absolute path to bin/agy-mcp from your clone.

User scope — available in every project on this machine. Most people want this.

claude mcp add agy --scope user -- /absolute/path/to/agy-mcp/bin/agy-mcp

Project scope — checked into the repo, shared with your team. Creates or updates .mcp.json in the project root.

claude mcp add agy --scope project -- /absolute/path/to/agy-mcp/bin/agy-mcp

The resulting .mcp.json:

{
  "mcpServers": {
    "agy": {
      "type": "stdio",
      "command": "/absolute/path/to/agy-mcp/bin/agy-mcp",
      "args": [],
      "env": {}
    }
  }
}

Local scope — this project only, not shared.

claude mcp add agy --scope local -- /absolute/path/to/agy-mcp/bin/agy-mcp

Then verify:

claude mcp list

Restart Claude Code after registering, and the six agy_* tools appear.

Tools

Difficulty tiers

Tiers resolve against the live model list from agy models, by pattern — highest version wins, broken ids are skipped. A new Gemini generation is adopted with no code change.

Model routing verification

agy has had model ids that silently route to a different backend — the flag is accepted, the response looks normal, and the model's own claim about its identity is not reliable. Confirmed on 1.1.7 and still present on 1.1.10:

gemini-3.1-pro-high   →  actually served by "Gemini 3.6 Flash (High)"
gemini-3.5-flash-low  →  actually served by "Gemini 3.5 Flash (Medium)"

Note that 1.1.10 shipped a fix for --model and --effort "being ignored ... so the run silently fell back to the persisted or default model". That is a different fault, and these two ids still misroute after it. The sibling ids gemini-3.6-flash-low and gemini-3.1-pro-low resolve correctly, which rules out flag ordering; what is left looks like effort variants that have no backend but are listed by agy models regardless, so agy serves the nearest one instead of failing. Trust the self-test, not the changelog.

This server runs every call with --log-file and parses agy's own line:

Propagating selected model override to backend: label="..."

The requested id and the reported label are compared by normalisation, not against a lookup table:

normalize(s) = s.toLowerCase().replace(/[^a-z0-9]/g, '')
match if normalize(label).startsWith(normalize(requestedId))

Because there is no hardcoded table, a routing bug introduced in a future agy build is caught the same way the known ones are. When a mismatch is detected the server names the model that actually answered, records it in ~/.local/state/agy-mcp/mismatches.json, and surfaces it in agy_models.

The two ids above are seeded as blocked and refused by default; pass force_broken_model to override and get an explicit warning instead of silent wrong-model output.

Security model

The reason there is a separate agy_exec tool is that MCP permission rules in Claude Code match on tool name only — there is no argument-level matching. If local execution were a boolean parameter on agy_ask, allowlisting agy_ask would allowlist arbitrary shell access.

So the capability is split:

• agy_ask and agy_research can never give agy shell or file access, whatever arguments are passed. Safe to allowlist.

• agy_exec is the only path to --dangerously-skip-permissions. Do not allowlist it. Let it prompt every time.

A suggested allowlist for ~/.claude/settings.json, deliberately excluding agy_exec:

{
  "permissions": {
    "allow": [
      "mcp__agy__agy_ask",
      "mcp__agy__agy_research",
      "mcp__agy__agy_result",
      "mcp__agy__agy_models",
      "mcp__agy__agy_selftest"
    ]
  }
}

What agy_exec does and does not enforce

workdirs is required and validated before agy is started. Every entry must be an absolute path to an existing directory; symlinks are resolved first, and the filesystem root, the home directory and system roots are refused outright — those are the over-scopes people reach for by accident. The first entry also becomes the working directory of the agy process, so relative paths resolve inside the scope. sandbox defaults to true, enabling agy's own terminal restrictions; the safer setting is what you get by not thinking about it.

Be blunt about the limit of all this: it constrains the invocation, not the agent. agy still runs with --dangerously-skip-permissions and has a shell. Writing "read-only" into the prompt is an instruction to the model, not an enforced sandbox — a request that will probably be respected, never a guarantee. This project does not claim to jail agy, and you should not describe it that way to your users.

Configuration

State (detected misroutings, background jobs) lives in ~/.local/state/agy-mcp/.

Known limitations

• The seeded broken-model list is tied to an agy version. It may be stale in either direction. Run agy_selftest after agy update to re-map.

• agy may decline remote-host work framed as a security audit. Describing the task accurately — your own machine, access already configured, a configuration inventory rather than a security analysis — is usually what was missing.

• /usage is not reachable headlessly. agy usage needs a real TTY; agy -p "/usage" returns a generic description, not real quota data.

• Headless agy cannot prompt for permission, which is exactly why file and shell work needs agy_exec.

• Parallel subagents in --print mode are real — each has a conversation tree under ~/.gemini/antigravity-cli/brain/<id>/ with genuine search grounding. The mechanism is trustworthy; individual figures can still be stale, so spot-check anything load-bearing.

Disclaimer

Unofficial and unaffiliated. Not endorsed by Google or Anthropic. "Antigravity", "Gemini", "Claude" and "Claude Code" belong to their respective owners; they are used here only to describe what this tool interoperates with.

License

MIT