A
licenseB
qualityB
maintenanceEnables calling Google's Antigravity CLI (agy) headlessly through MCP, providing tools like agy_ask and agy_research for agents like Claude Code.
2
43 PyPI
19
MIT
agy-mcp
by Boulea7
Related Servers
Alternatives to agy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceWraps 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
- AlicenseAqualityCmaintenanceBridges Google Antigravity CLI with MCP clients, enabling 13 specialized tools for AI-assisted coding, automation, and security audits.1317 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
A4/5.0
Scored across 11 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: agy/agy_continue/agy_start differentiate synchronous, resume, and background execution; agy_status/read/result/cancel/sessions cover distinct monitoring and control operations; and agy_doctor/install_skill/purge are separate admin utilities. Even the similar agy_read and agy_result are unambiguously separated by event log vs. captured output.
Naming Consistency4/5
All tools share the agy_ prefix and snake_case, creating a predictable namespace. However, the pattern mixes imperative verbs (start, read, cancel) with nouns (status, result, sessions), and the bare `agy` tool breaks the verb_noun convention. Despite this, the naming remains readable and internally consistent.
Tool Count5/5
With 11 tools, the server is well-scoped for its purpose, covering synchronous execution, background job lifecycle, monitoring, and admin functions without redundancy or bloat. This falls comfortably within the ideal 3-15 range.
Completeness4/5
The tool set provides comprehensive coverage of session and job lifecycle: run, continue, start, status, read, result, cancel, list, and purge. Minor gaps exist, such as no direct single-job delete or skill uninstall, but these are not critical to the core workflow and can be worked around.
Maintenance
ActivityInactive
ResponsivenessUnresponsive