Codex Antigravity Subagent MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTIGRAVITY_PERMISSION_MODE | No | Configure the permission mode for Antigravity CL. Default is 'auto-approve'. | auto-approve |
| ANTIGRAVITY_ENABLE_DASHBOARD | No | Set to '1' to launch the web dashboard concurrently with the MCP server. | 0 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delegate_to_geminiA | 通过 Antigravity CLI 调用 Gemini,默认模型为 gemini-3.8-flash-high。保留 prompt 并补充绝对工作目录,启用斜杠命令展开,可直接调用 /teamwork-preview <任务> 等系统命令。调用会等待结果;预计超过数分钟的 Teamwork 任务请使用 start_gemini_task。 |
| start_gemini_taskA | 后台启动 Antigravity/Gemini 任务并立即返回 job_id,适合 /teamwork-preview 等长任务。之后用 get_gemini_task 查询;后台任务依赖当前 MCP 服务进程保持运行。 |
| get_gemini_taskA | 按 job_id 查询后台 Gemini/Teamwork 任务状态和最终结果。 |
| cancel_gemini_taskA | 终止当前 MCP 进程中仍在运行的 Gemini/Teamwork 后台任务。 |
| interact_gemini_taskA | 向正在运行的长会话子代理(尤其处于 stream 模式的任务)注入交互式指令或人工输入,支持可选在完成当轮后优雅结束会话。 |
| finish_gemini_taskA | 主动结束处于 stream 模式的运行中任务,关闭 stdin 管道并等待任务优雅收敛进入 success 终态。 |
| antigravity_statusA | 检查 AGY CLI 版本、可用模型,以及默认模型 gemini-3.8-flash-high 是否存在。 |
| open_dashboardA | 在系统默认浏览器中打开独立的可视化监控看板(Web UI),实时展示全员子代理微观工作流、动作流与物理日志。 |
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 8 tools
Most tools target distinct actions: starting background tasks, starting synchronous tasks, querying, canceling, finishing, interacting, checking status, and opening the dashboard. The only mild ambiguity is between start/delegate and cancel/finish, but the descriptions clearly separate async vs sync and graceful vs hard termination.
The naming convention is largely consistent snake_case with verb_object patterns like start_gemini_task, get_gemini_task, and cancel_gemini_task. Minor deviations are delegate_to_gemini and antigravity_status, but they remain readable and predictable.
Eight tools is well-scoped for a task/subagent management server. Each tool covers a meaningful lifecycle or support function without unnecessary duplication or bloat.
The core lifecycle is covered: start sync/async, query status/results, cancel, finish, interact, and verify environment. A minor gap is the lack of a way to list all jobs or past tasks without knowing a job_id, though the dashboard partially compensates.