agy-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTIGRAVITY_MCP_AGY_PATH | No | Absolute path to the agy CLI executable, used if GUI apps cannot find agy. | |
| ANTIGRAVITY_MCP_JOBS_DIR | No | Directory to store job status files. Defaults to ~/.gemini/antigravity-mcp/jobs |
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 |
|---|---|
| run_antigravityA | Start a NEW task using Google Antigravity AI Agent (agy). Synchronous execution with a bounded timeout guard (auto-converts to a background job if still running). Supports YOLO autonomous execution or lightweight terminal sandboxing. |
| antigravity_continueA | CONTINUE an existing Antigravity conversation by ID. Synchronous execution with a bounded timeout guard (auto-converts to a background job if still running). Supports YOLO autonomous execution or lightweight terminal sandboxing. |
| antigravity_startA | Submit an asynchronous task to Antigravity and return a job ID without waiting for model completion. Use this for long-running tasks (e.g. multi-minute analyses, large refactors). Supports both new tasks and continuing existing sessions (if conversation_id is provided). |
| antigravity_job_statusA | Check the real-time progress and live step status of a background job. Fast local query (returns in < 20ms). Shows elapsed time, process alive status, and latest tool execution actions. |
| antigravity_job_resultA | Fetch the full execution report and final output of a background job once completed. Returns status, duration, full step trajectory, and final answer. |
| antigravity_job_cancelA | Cancel or kill an ongoing background Antigravity job by ID. |
| antigravity_sessionsA | List or search historical Antigravity sessions from local database (fast, zero model cost). Returns session IDs, summaries, step counts, and last modified times. Use this to find a conversation ID to resume. |
| antigravity_transcriptA | Read the detailed execution transcript of any past or current Antigravity session by ID. Fast local read (zero token cost). Returns the step-by-step history of user prompts, tools executed, command outputs, and conclusions. |
| antigravity_doctorA | Diagnose Antigravity CLI health, authentication token status, YOLO permission mode, and storage metrics. |
| antigravity_modelsA | List available models supported by this Antigravity installation. |
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 10 tools
Each tool has a distinct purpose: starting new tasks, continuing sessions, submitting async jobs, checking status, fetching results, canceling, listing sessions, diagnosing, reading transcripts, and listing models. There is no ambiguity between them.
The majority follow the 'antigravity_' prefix pattern with verb suffixes (e.g., antigravity_continue, antigravity_start). The one exception is 'run_antigravity', which inverts the order but remains clear. Overall, the naming is predictable and readable.
With 10 tools, the server is well-scoped for managing Antigravity agent tasks. Each tool serves a necessary function, covering execution, monitoring, history, diagnostics, and model discovery without bloat.
The toolset covers the full lifecycle of agent tasks: starting (sync/async), continuing, checking status, retrieving results, canceling, listing sessions, reading transcripts, and diagnosing the environment. No critical gaps are apparent for the intended domain.