agy-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGY_BIN | No | agy executable. Default: `agy` then `~/.local/bin/agy`. | agy |
| AGY_DENY | No | Permission deny rules. | |
| AGY_MODE | No | Conversation default mode. Default: agy defaults. | |
| AGY_ALLOW | No | Permission allow rules. | command(*),mcp(*) |
| AGY_MODEL | No | Conversation default model. Default: agy defaults. | |
| AGY_EFFORT | No | Conversation default effort. Default: agy defaults. | |
| AGY_IDLE_TTL | No | Hibernation TTL in seconds for idle conversations. | 1800 |
| AGY_WORKSPACE | No | Default workspace. Default: server cwd. | |
| AGY_ASK_TIMEOUT | No | Per-turn timeout in seconds. | 900 |
| AGY_BUSY_TIMEOUT | No | How long in seconds a second ask waits on a busy conversation. | 120 |
| AGY_MCP_PROGRESS | No | Set to `1` to stream deltas as MCP progress notifications. | 1 |
| AGY_SKIP_PERMISSIONS | No | Set to `1` for `--dangerously-skip-permissions`. | 0 |
| AGY_MAX_CONVERSATIONS | No | Maximum live agent processes (LRU). | 8 |
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 Google's Antigravity agent a question in the current persistent conversation. The agent keeps its memory across calls; it can use its native tools (shell, files, browser, web search) and any MCP servers registered in agy. Returns the agent's final answer. |
| agy_ask_newA | Same as agy_ask but starts a fresh conversation with no prior context. The previous default conversation stays alive and can be resumed with agy_resume. |
| agy_resumeA | Continue a previous conversation by id. Accepts either a conversation id returned by agy_ask/agy_ask_new or an agy conversation UUID (as shown in agy_conversations / agy's history). |
| agy_conversationsA | List the live conversations managed by this MCP server: ids, workspace, model, agy conversation id, and last use. |
| agy_stopA | Close the agent process for a conversation to free memory. The conversation's memory stays on disk and can be resumed later with agy_resume. Defaults to the current default conversation. |
| agy_modelsA | List the model ids the installed agy supports (cached 5 min). |
| agy_statusA | Report agy version, the signed-in account, configuration in effect, and the live conversations managed by this server. |
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 7 tools
The core trio (agy_ask, agy_ask_new, agy_resume) is clearly delineated by the persistent-vs-fresh-vs-resume distinction, and agy_stop/agy_models are unmistakable. The only soft overlap is agy_status vs agy_conversations, since status also reports live conversations, but the descriptions make the difference (diagnostics vs enumeration) reasonably clear.
All names share a uniform `agy_` prefix and snake_case, which makes the set highly predictable. The only minor wrinkle is the mixed verb/noun style (agy_ask/agy_resume/agy_stop vs agy_models/agy_conversations/agy_status), though that maps naturally to action vs listing tools.
Seven tools is a tight, well-scoped surface for a conversation-lifecycle wrapper around a single external agent. Each tool covers a distinct lifecycle step (start, fresh start, resume, list, stop, introspect models, introspect status) with no filler.
The conversation lifecycle is essentially covered: create, create-fresh, resume, list, stop, plus introspection of models and status. Gaps are minor but real: there is no way to pass a model selection into agy_ask despite agy_models existing, and no way to inspect or delete conversation history/messages.