A
licenseNot graded
qualityC
maintenanceEnables Claude Desktop to execute tasks via the Google Antigravity CLI (agy), exposing its models, skills, plugins, and background workers as native tools.
9
MIT
agy-headless-bridge MCP server
by rhishi99
Related Servers
Alternatives to agy-headless-bridge MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceWraps Google Antigravity CLI into 11 typed MCP tools, enabling any MCP client to invoke agy for code review, prototyping, execution, and long-running tasks.1134 PyPI23MIT
- FlicenseNot gradedqualityCmaintenanceWraps the Antigravity CLI (agy) as an MCP server, enabling Claude Code and other MCP clients to execute AI tasks and manage conversations via the agy command.-
- 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
- AlicenseAqualityDmaintenanceEnables Claude to drive the Antigravity agent by running prompts through the agy CLI non-interactively, supporting session management and optional sandboxed execution.51ISC
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible coding agents to run the local Antigravity CLI as a coding agent, manage conversation context and common options, and inspect usage, quota, models, version, help, and read-only slash commands.19 npmMIT
TDQS
B3.3/5.0
Scored across 2 tools
Disambiguation3/5
agy_ask and agy_research both send a prompt to the same Antigravity CLI and return a response, so the boundary is blurred: a user could fulfill research needs by calling agy_ask with a 'research this' prompt. The description hints at a depth/intent difference, but nothing structural distinguishes the two tools (no separate parameters, output shapes, or guarantees).
Naming Consistency5/5
Both tools use the same agy_ prefix with a single lowercase snake_case verb (ask, research), forming a clean, predictable pattern. There is no mixing of conventions or verb styles.
Tool Count3/5
Two tools is thin for a bridge server, and one of them (agy_research) appears to be a thin wrapper around the other, so the surface feels under-scoped rather than deliberately minimal. It is not extreme, but there is little room for distinct capability.
Completeness3/5
The server covers one-shot prompt delegation but lacks any session/multi-turn continuation, file or workspace context parameters, or status/cancel operations that a CLI bridge typically needs. Core workflow (ask something and get an answer) works, but agents will hit dead ends for stateful or long-running tasks.
Maintenance
ActivityMaintained
ResponsivenessNo issues