Antigravity Integration

⚡ 5 min read

Connect Transcodes step-up MFA and MCP tools to Google Antigravity 2.0 via the Transcodes Guard plugin.

Package: @bigstrider/transcodes-guard-antigravity (hooks + MCP) · CLI: transcodes for enable/disable and tokens

Prerequisites

AI Agent Overview — Transcodes project and member token
Node.js 18+
Antigravity 2.0 with plugin / MCP support enabled

Install the plugin

Install from the Transcodes Guard release (or your org’s plugin marketplace bundle). The plugin registers:

PreToolUse — intercepts risky shell commands and protected MCP tools
PreInvocation — session start + prompt submit (merged lifecycle)
Stop — session end cleanup

Step-up MFA runs against auth.transcodes.io before the gated action proceeds.

Configure MCP (optional)

If you use the Transcodes MCP server alongside the guard plugin, add the same transcodes MCP block as Cursor — Antigravity accepts the standard mcpServers JSON shape with TRANSCODES_TOKEN.

Enable the gate


npx @bigstrider/transcodes-cli enable
npx @bigstrider/transcodes-cli tokens

Store tokens via the CLI; hooks read from ~/.transcodes/config.json. Disabling the gate requires a human (transcodes disable).

Antigravity uses a different hook stdin/stdout contract than Claude Code. The Guard plugin ships host-specific adapters — you do not wire hooks manually.

Verified MCP actions

Risky tools (e.g. retire_member, suspend_member, passcode_create) trigger step-up auth before execution. RBAC on the token’s member determines which tools are available — see RBAC.

See also: Step-up Auth · Audit Logs