SYSTEM 01 / ANTIGRAVITY MCP NODE

Antigravity MCP Node Full-Stack Flow

Remote IDE intent enters through a private MCP endpoint, crosses a Node service boundary, executes against local host resources, then returns structured evidence back to the client.

Stack layers full path from input to output
01Antigravity IDE
02Tailscale private IP
03HTTP streamable MCP
04Node MCP server
05local filesystem
06shell/runtime tools
07logs/evidence
Architecture graph

Control plane + data plane + trust boundaries

Live log: antigravity-mcp 2.20.0 listening on http://100.90.87.7:3000/mcp; local process scan confirmed Node/MCP/Hermes-adjacent services.

user Antigravity IDE

agent UI, prompt, tool intent

edge Tailscale edge

100.90.87.7 private route

runtime antigravity-mcp

Node service /mcp on :3000

guard Tool schema layer

capabilities, params, returns

data Local project files

repo, config, generated assets

ai Local execution

commands, scripts, diagnostics

output Evidence channel

stdout, stderr, audit logs

guard Trust boundary

remote intent vs local authority

Runtime sequencehow data moves
  1. 1. Session

    IDE opens MCP connection over the private tailnet address and receives server capabilities.

  2. 2. Selection

    The client chooses a tool and sends typed arguments; schema validation is the first control point.

  3. 3. Execution

    The Node MCP layer bridges into local host resources only for the requested capability.

  4. 4. Evidence

    Tool output is converted into concise return data, with logs retained for debugging and audit.

Data contractssource → transform → destination
Prompt intent

Antigravity IDE→MCP tool selection→Node MCP server

Tool arguments

MCP request→schema + boundary validation→local action

Execution result

filesystem / shell→stdout/stderr/result shaping→MCP response

boundary

Network boundary

Private Tailscale address, not a public internet route.

boundary

Execution boundary

MCP requests can represent local actions; tool scope matters more than port health.

boundary

Data boundary

Return evidence should be narrow: status, files touched, logs, and errors instead of raw secrets.