Antigravity Headless Bridge

io.github.rhishi99Published by GitHub account rhishi99v1.3.0Updated Oct 24, 2026

Call Google's Antigravity CLI (agy) headlessly from non-TTY contexts (subprocess, MCP, CI).

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Lets an assistant invoke Google's Antigravity CLI (agy) headlessly from non-interactive contexts such as subprocesses, MCP, and CI.

What you can do
This server bridges an AI assistant to Google's Antigravity CLI (agy) so it can be driven without an interactive terminal. It is aimed at non-TTY contexts, meaning subprocess calls, MCP clients, and CI pipelines. The manifest lists no tools, so the exact commands exposed are not documented here.
When to use it
Worth adding when you already use the Antigravity CLI and want an assistant or an automated pipeline to run it without a terminal attached. It is a desktop-only local process, so it suits developer machines and CI runners rather than hosted or browser-based setups.
Requirements
Runs as a local process over stdio, installed from the PyPI package agy-headless-bridge, so a Python runtime is needed. The Antigravity CLI (agy) must be available on the machine. No authentication, environment variables, or headers are declared.
Before you install
The manifest declares no credentials, but the server executes the Antigravity CLI on your machine, so anything that CLI can do — including writing files or running commands — may be triggered through it. Review what the underlying CLI is permitted to do before connecting it to an assistant or CI job.

Installation

In SourceWeft

  1. Open Antigravity Headless Bridge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.3.0LatestSep 26, 2026
  2. v1.0.1Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.