claude-to-agy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGY_TOTAL_TIMEOUT | No | Hard timeout for entire execution | 1200 |
| AGY_CONNECT_TIMEOUT | No | Seconds to start the agy process | 60 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delegate_to_agyB | Delegate complex reasoning or deep search to Antigravity CLI. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
The tool name follows a clear verb_noun pattern ('delegate_to_agy'), consistent with common conventions. With only one tool, naming consistency is inherent.
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.
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.