Claude Agy MCP

What claude-agy-mcp does

The claude-agy-mcp MCP server connects Claude Code to Google's Antigravity CLI, referred to as agy in the project documentation. Claude Code remains the orchestrator while agy handles delegated work using the model chains assigned to each tool. Results are returned to Claude Code rather than requiring the full source material or command output to remain in its context.

The project is aimed at software-engineering tasks that are expensive to inspect directly, including large file analysis, deep searches through repositories, web lookups, broad delegation, and adversarial code review. The README also describes use with raw execution-oriented workloads and repository archaeology such as git history, diffs, and blame.

How it works

The claude-agy-mcp MCP server runs as a stdio MCP process and invokes the locally available Antigravity CLI. Task tools use ordered model chains. For example, analyze_files starts with gemini-flash@latest-high and falls back to gemini-pro@latest-low; adversarial_review can continue from Gemini Flash to Gemini Pro and then Claude Opus. These model identifiers resolve through agy models, so the bridge follows the models available through that CLI rather than pinning one generation.

follow_up reuses the active agy session, allowing a later question to continue a delegated conversation without resending the original context. Quota or availability conditions can cause a tool to move to the next model in its chain. set_model and agy_status are local MCP operations and do not invoke agy.

Setup and configuration

Install the npm package with:

npm i @pymodel/claude-agy-mcp

Register it with Claude Code as a stdio server:

claude mcp add-json -s user claude-agy-mcp \
  '{"type":"stdio","command":"npx","args":["-y","@pymodel/claude-agy-mcp"],"timeout":3600000}'

The documented configuration uses npx to start the package and sets a one-hour MCP timeout. The provided material does not specify required environment variables or additional configuration files.

Tools and capabilities

The available tools are:

• analyze_files: Analyze files with Flash first, then Pro at low effort.
• deep_search: Search deeply with Flash high effort, then Flash medium effort.
• web_lookup: Perform a web lookup using the same Flash fallback chain.
• adversarial_review: Run a review through Flash, Pro, and then Claude Opus if needed.
• follow_up: Continue the current agy session.
• delegate: Send a general task through Flash and Pro fallback models.
• delegate_many: Delegate through Flash, Pro, and Claude Opus fallback stages.
• set_model: Change the selected model without reaching agy.
• agy_status: Check status without reaching agy.

Limitations and notes

The claude-agy-mcp MCP server depends on the Antigravity CLI and the models that CLI exposes. Model names such as gemini-flash@latest-high are family and effort selectors, not fixed generation pins. The README states that Gemini Flash is the default starting point and that later models are used when Flash is unavailable or cooling down.

Returned output is intended to keep Claude Code's context focused, but the material does not define a universal response-size guarantee. The listed fallback behavior is tool-specific, so applications should account for different model paths across operations. The supplied documentation names Claude Code as the orchestrating client; it does not provide client-specific setup instructions for other MCP hosts.