A thin, auditable MCP server wrapping the Antigravity CLI (agy). Forward-compatible with future CLI flags via extra_args passthrough.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"antigravity-cli-mcp-slim","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# antigravity-cli-mcp-slim A thin, auditable [MCP](https://modelcontextprotocol.io) server wrapping the [Antigravity CLI](https://github.com/google-antigravity/antigravity-cli) (`agy`). [](https://pypi.org/project/antigravity-cli-mcp-slim/) [](https://pypi.org/project/antigravity-cli-mcp-slim/) [](https://opensource.org/licenses/MIT) [](https://github.com/tksfjt1024/antigravity-cli-mcp-slim/actions/workflows/ci.yml) ## Why When you add an MCP server to your AI coding tool, every prompt and code snippet you send flows through that wrapper. Most CLI-wrapping MCP servers are small, individually maintained packages — and recent supply-chain incidents (`xz-utils`, `postmark-mcp`, the npm `chalk`/`debug` compromise) show that "small and useful" is not the same as "safe to trust blindly." This project takes the opposite stance: instead of asking you to trust it, it tries to be **easy to audit**. - **Single file** — the whole server is `src/antigravity_cli_mcp_slim/server.py`, readable end-to-end in one sitting - **One third-party dependency** (`mcp`) — minimal supply-chain surface - **Faithful CLI mapping** — every typed parameter mirrors a real `agy` flag by name, so it is obvious which flags an invocation actually sets - **Forward-compatible** — any new or uncommon `agy` flag is reachable via `extra_args` without touching this server - **Configurable binary path** — `$AGY_CMD` lets you swap or wrap the `agy` binary - **Transparent** — every invocation logs the exact argv to stderr Read `server.py` before you install. That is the point. ## Prerequisites - The `agy` CLI, **version 1.1.8 or newer**, installed and on `$PATH` (or pointed …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.