agy-headless-bridge MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGY_PATH | No | Absolute path to the agy binary. If not set, auto-detected. | |
| AGY_BRIDGE_TIMEOUT | No | Seconds before a call is killed. | 180 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agy_askA | Send a one-shot prompt to the Google Antigravity CLI (agy) and return its response. Use to delegate a focused coding, debugging, or reasoning task to Gemini via Antigravity. |
| agy_researchB | Ask Antigravity to research a topic deeply. |
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 2 tools
The two tools are clearly described: agy_ask for focused tasks and agy_research for deep research. While both use the same underlying CLI, their purposes are distinct enough that an agent should not confuse them.
Both tools follow a consistent agy_verb naming pattern with snake_case, making the intention clear and predictable.
With only two tools, the server feels very limited. For a CLI bridge, one would expect more operations like configuration, listing, result retrieval, etc. The count is at the low end of acceptable for a minimal server.
The tool surface is extremely sparse. There are no tools for managing sessions, inspecting state, or handling errors, which are important for a headless bridge. Agents may hit dead ends without broader coverage.