gemini2codex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGY_MODEL | No | Model used for writing tasks. Defaults to gemini-3.8-flash-medium. | |
| AGY_COMMAND | No | Absolute executable path to the Antigravity CLI (agy). If not set, agy must be available in your PATH. | |
| GEMINI_API_KEY | No | Google Gemini API key, required when WRITER_PROVIDER=gemini-api. | |
| AGY_AGENT_MODEL | No | Model used for the default implementation tasks. Defaults to gemini-3.8-flash-high. | |
| WRITER_PROVIDER | No | Set to gemini-api to connect directly to the official Google Gemini API instead of the local CLI. Must be set together with GEMINI_API_KEY and GEMINI_API_MODEL. | |
| GEMINI_API_MODEL | No | Gemini API model to use when WRITER_PROVIDER=gemini-api; must support the required thinking level. |
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 |
|---|---|
| gemini_spawn_agentA | Spawn a Gemini subagent, like Codex spawn_agent. Defaults to frontend / Gemini 3.8 Flash High. Specify task_name, message, existing absolute workspace and capabilities. Returns a durable id used as target for communication and follow-ups. Supply a stable idempotency_key to safely resubmit after an uncertain disconnect; the same key and request return the original task without executing again. Fixed command grants have local user privileges; inspect them before granting. permissions.native_tools=true explicitly enables provider native tools beyond fixed grants and requires write=true. Native effects are not tracked; independently verify the final report. |
| gemini_send_messageB | Send a message to a named or identified Gemini agent. JSON-mode agents discard stale proposed actions. Native-mode agents finish the current request before reading steering; native changes remain. Waiting agents resume when supplied an answer; completed agents retain messages without starting a run. |
| gemini_followup_taskA | Continue work on the same Gemini agent and retained context. Idle agents start a new run; running agents receive steering at the next boundary. Workspace and capabilities stay fixed. |
| gemini_list_agentsA | List retained Gemini agents with names, stable IDs, status, messages, revisions and reports. Tasks and results survive MCP reconnection and remain available for follow-up. |
| gemini_wait_agentA | Observe agy execution, tool activity, elapsed/silent time, messages and results. Pass returned revision as after_revision and compact=true for incremental events. until=update returns on new progress; until=attention streams MCP progress notifications while waiting for completion, input or a Gemini message. Bounded wait; no provider requests or retries. |
| gemini_interrupt_agentA | Interrupt a Gemini agent and stop active work. The agent remains available for follow-up with retained context; existing file changes remain. |
| gemini_agent_submitA | Delegate an autonomous frontend/general/writing task. Frontend and general use highest available thinking (high), writing uses medium. Default JSON-mode reads are scoped to workspace; writes require write=true. Explicit native_tools=true enables provider native tools with local user privileges, requires write=true, and does not track native effects. Commands grant an exact executable and fixed args; they run with local user privileges and must be reviewed before granting. Returns a task ID immediately; poll status for progress and results. |
| gemini_agent_statusA | Read durable task status, progress events, changed files, command exit codes, structured failure or final report. Tasks survive MCP reconnection; structured errors include failure_reason, retryable, error_id, explicitly incomplete partial output and recovery guidance when available. Completion records the agent report; independently check files and validation. |
| gemini_agent_cancelA | Cancel a queued or running task and stop its active process tree. Previously completed file changes remain for review. |
| gemini_writeB | Write prose from authoritative facts. One call per writing unit. Codex must check facts before final use. |
| gemini_polishC | Polish expression while preserving facts, numbers, names, URLs, paths, commands and identifiers. |
| gemini_rewriteC | Restructure prose while preserving facts and literal technical content. Do not repeatedly polish the result. |
| gemini_reviewB | Compare original and revised prose for fact drift and omissions. Structured editorial feedback; Codex remains the factual authority. |
| gemini_healthA | Explicit live provider probe: executable, authentication, exact model listing and READY generation. Unknown states are null. |
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 14 tools
There are multiple overlapping pairs: gemini_spawn_agent vs gemini_agent_submit both start Gemini work, gemini_send_message vs gemini_followup_task both communicate with an existing agent, gemini_wait_agent vs gemini_agent_status both observe progress/results, and gemini_interrupt_agent vs gemini_agent_cancel both stop work. Descriptions help distinguish agent-oriented from task-oriented flows, but an agent can easily misselect between the parallel APIs.
All names use the gemini_ prefix and snake_case, but the action/resource ordering is inconsistent: gemini_spawn_agent, gemini_list_agents, gemini_wait_agent, and gemini_interrupt_agent use verb_noun, while gemini_agent_submit, gemini_agent_status, and gemini_agent_cancel use noun_verb. Prose tools like gemini_polish, gemini_rewrite, gemini_review, and gemini_write also break the agent/task noun pattern, making the naming scheme only partially predictable.
Fourteen tools is within a reasonable range for a server covering agent lifecycle, task lifecycle, prose operations, and health checks. The count is slightly inflated by two overlapping lifecycle families, but it is not excessive for the apparent scope.
The surface covers agent spawn/list/message/follow-up/wait/interrupt, task submit/status/cancel, prose write/polish/rewrite/review, and health probing. However, task listing is missing, and agent lifecycle lacks an explicit get/delete or terminate operation, which can create recovery gaps if IDs are lost or stale agents accumulate.