Agy MCP Server

MCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — purpose-built tools, model routing with fallback, and multi-turn

Local serverstdioPython

What is the Agy MCP server?

MCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — purpose-built tools, model routing with fallback, and multi-turn session continuity. Exposed over MCP by the agy mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

An MCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — saving Claude's context window and tokens for what matters.

Its toolset

Everything the assistant can do here goes through one of these:

  • analyze_files — Files >200 lines, >3 files at once, logs, dumps, generated code
  • deep_search — git log/diff/blame archaeology, repo-wide greps
  • web_lookup — Docs, API references, external/current knowledge
  • adversarial_review — Plan critiques, design and code reviews
  • follow_up — Continue a prior session by session_id — no context resend
  • delegate — Anything else heavy

Configuration

Adding it to your client

The server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Agy's toolset — analyze_files, deep_search, web_lookup and 3 more — is a fair guide to whether it matches your workflow. It is maintained by sshahzaiib; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the agy mcp server does with a few real requests.

Available tools

ToolWhat it does
analyze_filesFiles >200 lines, >3 files at once, logs, dumps, generated code
deep_searchgit log/diff/blame archaeology, repo-wide greps
web_lookupDocs, API references, external/current knowledge
adversarial_reviewPlan critiques, design and code reviews
follow_upContinue a prior session by session_id — no context resend
delegateAnything else heavy

How to install the Agy MCP server

{
  "mcpServers": {
    "agy-bridge": {
      "command": "npx",
      "args": ["-y", "npm"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

Example prompts to try

  • Use Agy to analyze files.
  • Use Agy to deep search.
  • Use Agy to web lookup.

Frequently asked questions

It connects Agy to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (analyze_files, deep_search, web_lookup, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Agy directly.