tphakala/agy-mcp

一个MCP（模型上下文协议）服务器，包裹了Antigravity CLI（agy），因此任何MCP客户端（Claude Code、Cursor、Cline等）都可以作为原生工具运行agy提示、同行评审和跟进。

状态：功能已完成（stdio和HTTP传输、异步和同步作业生命周期、模型和会话发现、每次运行控制和结构化输出、跨平台构建），并已通过实时AGY验证，最低支持版本为1.1.15。

为什么

从壳层驱动agy进行自动化运行存在两个反复出现的问题：

• agy -p（打印模式）即使提示以-p传递，仍读取stdin。如果stdin是一个永不关闭的开放管道，它会无限阻塞。解决方法是始终关闭stdin（ ），这样线程在调用间存活，无需保持进程温热。

委派运行可以修改你的文件。 agy 启动时 --dangerously-skip-permissions，因此它启动的代理可以读写在以下的任何位置 cwd，并且在dirs中每个目录下方都经过，无需提示。对于必须进行的审查 不要碰仓库，在提示中明确说明。工具在线路上声明：agy_run 和

An MCP (Model Context Protocol) server that wraps the Antigravity CLI (agy), so any MCP client (Claude Code, Cursor, Cline, and others) can run agy prompts, peer reviews, and follow-up turns as native tools.

Status: feature complete (stdio and HTTP transports, async and sync job lifecycle, model and session discovery, per-run controls and structured output, cross-platform builds) and verified against a live agy, with 1.1.15 the minimum supported version.

Why

Driving agy from a shell for automation has two recurring problems:

• agy -p (print mode) reads stdin even when the prompt is passed with -p. If stdin is an open pipe that never closes, it blocks indefinitely. The fix is to always close stdin (</dev/null), which is easy to forget.
• A review can run for many minutes. A single blocking call ties up the caller and can exceed a client’s tool-call timeout with nothing recoverable.

agy-mcp solves both by running agy as managed, asynchronous jobs behind a small, typed tool surface, and by capturing output to disk, with a completed run’s result and metadata fsync’d, so the result survives a client disconnect, a server restart, or a crash.

Every job runs agy --output-format stream-json, and the supervisor decodes that event stream as it arrives. That is where the conversation id, the response text, the failure message, and the token accounting all come from, so agy-mcp never has to infer any of them.

What it provides

• agy_run / agy_status / agy_cancel: start an agy prompt, poll for completion, cancel if needed.
• agy_run_sync: start a prompt and wait for it inline (bounded, with MCP progress notifications); returns the job_id to wait on or poll if it outlives the wait cap.