agy-mcp
Related Servers
Alternatives to agy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables calling Google's Antigravity CLI (agy) headlessly through MCP, providing tools like agy_ask and agy_research for agents like Claude Code.2115 PyPI19MIT
- AlicenseAqualityDmaintenanceWraps Google's Antigravity CLI as MCP tools for Claude, enabling cost-disciplined multi-model execution with background jobs and fan-out research/review pipelines.13MIT
- AlicenseAqualityDmaintenanceBridges Google Antigravity CLI with MCP clients, enabling 13 specialized tools for AI-assisted coding, automation, and security audits.1321 npmMIT
- AlicenseBqualityCmaintenanceExposes the Antigravity CLI to MCP clients for structured planning, code review, test validation, general prompts, and literal slash commands against Google Gemini models.5MIT
- AlicenseBqualityBmaintenanceEnables MCP-compatible AI clients like Claude Code, Cursor, and Codex to invoke Google Antigravity's Gemini coding agent for repository-aware file operations, command execution, code review, test generation, and quota checks, while also providing a standalone dual-mode CLI.7MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI clients to run Google Antigravity coding sub-agents as MCP tools, with synchronous and asynchronous execution, task polling, and sandboxed Docker workspace isolation.-
TDQS
Scored across 11 tools
Each tool has a clearly distinct role: synchronous run vs background start vs continue, and job inspection is split into status, result, read, and sessions with descriptions that explain the boundaries. The overlap around job state/output is minimal and resolvable from the descriptions.
Names are consistently snake_case with an agy_ prefix, except for the main tool named simply 'agy' as a legacy drop-in. The verb/noun mix (start, read, cancel vs status, result, sessions) is readable but not a single uniform pattern.
Eleven tools is well-scoped for an MCP wrapper that manages background jobs, synchronous runs, sessions, diagnostics, and skill installation. Each tool appears to earn its place without obvious redundancy.
The surface covers the core job lifecycle: start, run, continue, status, read, result, cancel, list, and purge, plus diagnostics and skill installation. Minor gaps exist, such as no explicit single-job deletion or skill uninstall/update operation, but agents can work around them.