agy-mcp
Related Servers
Alternatives to agy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAllows Claude Code to request an independent code review from Google Antigravity (Gemini, Claude, or GPT-OSS) via the Antigravity CLI, providing a second opinion on plans or diffs.182 npm2MIT
- AlicenseAqualityDmaintenanceEnables Claude to drive the Antigravity agent by running prompts through the agy CLI non-interactively, supporting session management and optional sandboxed execution.51ISC
- AlicenseAqualityDmaintenanceWraps Google Antigravity CLI into 11 typed MCP tools, enabling any MCP client to invoke agy for code review, prototyping, execution, and long-running tasks.1123MIT
- FlicenseAqualityDmaintenanceEnables Claude to create, manage, and clean up git worktrees automatically, including dependency installation and GitHub PR creation.5-
- AlicenseBqualityBmaintenanceEnables calling Google's Antigravity CLI (agy) headlessly through MCP, providing tools like agy_ask and agy_research for agents like Claude Code.243 PyPI19MIT
- AlicenseAqualityBmaintenanceMCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — purpose-built tools, model routing with fallback, session continuity, and output truncation to save Claude's context and tokens.6111 npm51MIT
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: ask is read-only Q&A, execute is write-capable task execution in an isolated worktree, list_sessions enumerates sessions, and close_session terminates them. There is no meaningful overlap; even ask and execute are sharply differentiated by their mode and permissions.
All tools share the agy_ prefix and use imperative verbs, but agy_ask and agy_execute omit an explicit object while agy_list_sessions and agy_close_session include one. The pattern is predictable and readable, with only a minor inconsistency in verb-phrase structure.
Four tools is on the lean side but appropriate for a focused server that wraps agy CLI session management. Each tool covers a distinct operation (ask, execute, list, close), so none feel redundant or missing.
The tool set covers the full session lifecycle: start an ask or execute session, continue one via session_id, list all sessions, and close/delete them. Minor gaps exist (no dedicated 'get session details' tool, no way to modify a session's plan), but list_sessions provides sufficient visibility and the ask/execute tools accept session_id to continue, so agents can work around these.