agy-mcp
Related Servers
Alternatives to agy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to delegate implementation tasks to Antigravity CLI and OpenCode, run them fully autonomously, and then review and gate the results.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to delegate tasks to Google Antigravity (Gemini) as an autonomous subagent, including codebase exploration, architecture analysis, multi-file code generation, and technical Q&A, without requiring external API keys.MIT
- AlicenseAqualityCmaintenanceEnables Claude to delegate tasks to external coding agents (Codex or Antigravity) for independent reviews, separate quota usage, and async processing.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables a primary agent in Antigravity IDE to delegate coding tasks to background subagents across multiple model backends, with crash recovery, process cleanup, and human-in-the-loop approval for destructive actions.MIT
- AlicenseAqualityBmaintenanceEnables Codex to delegate bounded code analysis, review, isolated edits, multimodal research, and native image generation to supervised Antigravity workers, with queued execution, retries, and inspectable patches.232MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to hand off bulk, mechanical, read-heavy tasks to a local model, including agentic loops that can read, write, and run commands sandboxed at zero cloud token cost.MIT
TDQS
Scored across 12 tools
The agy_* and codex_* families have parallel execute/continue/check/status tools that can be confused, especially since codex_check_task explicitly says it handles both Codex and Antigravity tasks. Prefixes and descriptions help, but the duplicate lifecycle across two similar agent types creates real ambiguity.
All tools follow a consistent provider_prefix + verb pattern using snake_case, such as agy_execute, codex_check_task, and chatgpt_review. This makes the tool set predictable and easy to navigate.
Twelve tools is within a reasonable range for a multi-provider delegation server. The count is slightly inflated by parallel lifecycle tools for agy and codex, but each provider family has a clear purpose.
The tool surface covers the core delegation workflow: execute, continue, check status, inspect transcripts, and get provider status. Minor gaps exist, such as no explicit cancellation or session listing, but agents can complete primary tasks without dead ends.