antigravity-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | No | Enables the Gemini REST fallback when the IDE is not running. | |
| GOOGLE_API_KEY | No | Enables the Gemini REST fallback when the IDE is not running (alternative to GEMINI_API_KEY). | |
| ANTIGRAVITY_MOCK | No | Enable the mock backend. Only when explicitly set to 1. | unset |
| ANTIGRAVITY_LOG_LEVEL | No | Server log level on stderr. | INFO |
| ANTIGRAVITY_STATE_DIR | No | Where job history is kept. | platform state dir |
| ANTIGRAVITY_JOB_TIMEOUT | No | Seconds before a job is abandoned. Finishing early is detected, not waited out, so a generous ceiling costs nothing. | 1800 |
| ANTIGRAVITY_DISABLE_LOCAL | No | Skip the local backend entirely. | unset |
| ANTIGRAVITY_MAX_CONCURRENT_JOBS | No | Jobs running at once. Every job drives a live session on the same language server process, so this is a real resource ceiling, not a formality. Extra jobs queue. | 3 |
| ANTIGRAVITY_MAX_CONCURRENT_REQUESTS | No | Tool calls handled in parallel. | 16 |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dispatch_gemini_agentA | Dispatch a coding, analysis, or research task to a background Antigravity subagent. Returns immediately with a job_id so the orchestrator is never blocked. |
| list_available_modelsA | List the live models currently available from the connected Antigravity IDE session. Call this before dispatch_gemini_agent when you do not already know an exact, currently-live model name. |
| check_agent_jobB | Check the status, logs, duration, and output of a dispatched agent job. |
| list_active_jobsC | List active, pending, completed, cancelled, or failed subagent jobs. |
| cancel_agent_jobB | Cancel a running background subagent job. |
| gemini_code_searchB | Use a large-context model to scan multiple repository files at once and answer architectural or code questions about them. Runs synchronously and returns the answer. |
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 6 tools
Most tools are clearly distinct: dispatch/check/list/cancel form a clean job-management set, and list_available_models is unique. The main soft spot is gemini_code_search vs dispatch_gemini_agent, since both invoke Gemini to reason over code, though the sync-scan vs async-agent distinction in the descriptions mostly resolves it.
Five of six names follow a clean verb_noun pattern (dispatch_gemini_agent, list_available_models, check_agent_job, list_active_jobs, cancel_agent_job). gemini_code_search breaks the convention by leading with the noun/qualifier rather than a verb, a minor deviation in an otherwise consistent set.
Six tools is well-scoped for an orchestration server covering sync code Q&A, async dispatch, model discovery, and job lifecycle management. Each tool earns its place with no redundant or filler operations.
The subagent job lifecycle is well covered (dispatch, check status/logs/output, list, cancel), plus code search and model listing. Minor gaps remain, such as no explicit job-resume/retry or log-streaming tool, but agents can work around these.