agy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| agy_askA | Ask agy (Antigravity CLI) a question or for a second opinion. Read-only: agy runs in --mode plan and cannot edit files. Pass session_id to continue a prior conversation with full context; omit it to start a new one. Alternatively pass conversation_id to adopt an existing agy CLI conversation (e.g. one you started in your own terminal) that this server didn't create — note this only works for agy CLI conversations, not Antigravity IDE ones. |
| agy_executeA | Hand a plan/sprint to agy (Antigravity CLI) to execute with full file-write permissions. Runs inside an isolated git worktree (never the real working tree) so changes can be reviewed before merging. Pass session_id to continue a prior execute session in its existing worktree; omit it to start a new one. Alternatively pass conversation_id to adopt an existing agy CLI conversation (e.g. one you started in your own terminal) into a fresh worktree — note this only works for agy CLI conversations, not Antigravity IDE ones. Requires AGY_MCP_ALLOW_EXECUTE=1 in the server's environment. |
| agy_list_sessionsA | List known agy sessions (both ask and execute) with their status, workspace, and worktree path. |
| agy_close_sessionA | Close a session. By default this only marks it closed and leaves any worktree/branch on disk for manual review; pass remove_worktree=true to also delete the worktree (irreversible, discards any uncommitted changes in it). |
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 4 tools
Each tool has a clear, distinct purpose: ask is read-only Q&A, execute is write-capable task execution in an isolated worktree, list_sessions enumerates sessions, and close_session terminates them. There is no meaningful overlap; even ask and execute are sharply differentiated by their mode and permissions.
All tools share the agy_ prefix and use imperative verbs, but agy_ask and agy_execute omit an explicit object while agy_list_sessions and agy_close_session include one. The pattern is predictable and readable, with only a minor inconsistency in verb-phrase structure.
Four tools is on the lean side but appropriate for a focused server that wraps agy CLI session management. Each tool covers a distinct operation (ask, execute, list, close), so none feel redundant or missing.
The tool set covers the full session lifecycle: start an ask or execute session, continue one via session_id, list all sessions, and close/delete them. Minor gaps exist (no dedicated 'get session details' tool, no way to modify a session's plan), but list_sessions provides sufficient visibility and the ask/execute tools accept session_id to continue, so agents can work around these.