Antigravity Link MCP Server

Antigravity Link MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server and OpenAPI-backed mobile companion for controlling Antigravity IDE sessions.

What you get

You're running an Antigravity session and need to step away from your desk. The AI is mid-generation. You want to monitor it, redirect it, upload a file, or just read what it wrote from your phone, without coming back to your computer.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Antigravity Link is connected, these are the calls the assistant has available:

• Method — Endpoint
• GET — /ping
• POST — /instance

Configuration and credentials

You will need 2 environment variables: AG_BRIDGE_URL, AG_BRIDGE_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Antigravity IDE installed and running. - A phone and computer on the same Wi-Fi network. - Antigravity launched with the remote debugging flag. This is required for the extension to discover and connect to your session. See the launch command in Quick start below.

Before you rely on it

• 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.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the antigravity link mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Antigravity Link's toolset — Method, GET, POST — is a fair guide to whether it matches your workflow. It is maintained by cafeTechne; 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.