Mark's Reports

status · 2026-04-13

Antigravity MCP Config Hunt — Findings

Date: 2026-04-13

Task: Locate Antigravity's MCP server config and add twin-memory so Antigravity has cross-Claude shared memory parity with G16 + Apex Claude Code.

Where Antigravity actually keeps its MCP config

Live path (Windows): C:\Users\Breez\.gemini\antigravity\mcp_config.json

WSL path (same file): /mnt/c/Users/Breez/.gemini/antigravity/mcp_config.json

Antigravity is built on a VS Code fork and lives at C:\Users\Breez\AppData\Local\Programs\Antigravity\, with profile data in C:\Users\Breez\AppData\Roaming\Antigravity\. But the MCP config is NOT in the Antigravity profile dir — it is stored under the .gemini namespace alongside Gemini Code Assist state. That's why earlier searches missed it.

The Antigravity tree contains an extensions host plus a Cline-style file at …\Roaming\Antigravity\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json — that's the Cline extension's MCP config, NOT Antigravity-native. Ignore it.

A history snapshot at …\Antigravity\User\History\-4a0f9931\entries.json confirms Antigravity itself reads and edits file:///c:/Users/Breez/.gemini/antigravity/mcp_config.json. Confirmed.

Current state of the file

The file already contains 5 servers: omi, apex-node, twin-memory, chrome-devtools-mcp, gmp-code-assist.

Good news: twin-memory is already wired in.

Bad news: the token is STALE.

SourceToken (first 12 chars)
Antigravity mcp_config.json (current)43685a32a15a…
G16 Claude Code ~/.claude.json (working)7ee7f2f28744…

Antigravity's twin-memory entry is currently failing auth against omi-mcp.thebarnetts.info/rpc. To restore parity, only the token needs updating — no schema change, no new entry.

Format note (Antigravity vs Anthropic)

Antigravity uses the Gemini-CLI flavor of mcpServers schema, NOT the Anthropic schema. The HTTP-server key is serverUrl (Anthropic uses url), and there's no "type": "http" field. The existing twin-memory block uses Antigravity's correct shape:


"twin-memory": {
  "serverUrl": "https://omi-mcp.thebarnetts.info/rpc",
  "headers": {
    "X-TP3-MCP-TOKEN": "<token>",
    "Content-Type": "application/json"
  },
  "trust": true
}

So the proposed change is a token swap only, leaving the schema intact.

Proposed edit (diff)


     "twin-memory": {
       "serverUrl": "https://omi-mcp.thebarnetts.info/rpc",
       "headers": {
-        "X-TP3-MCP-TOKEN": "43685a32a15aa8c59532e09c97e6368f22777e841ac857ee8c6584e7bd64e1a8",
+        "X-TP3-MCP-TOKEN": "7ee7f2f28744847727023cab0147749c83172018bfea0cd6fed6589a4d42fc6b",
         "Content-Type": "application/json"
       },
       "trust": true
     },

No other keys change. No other servers touched.

One-line apply command (review first, then run from G16 WSL)


python3 -c "import json,pathlib; p=pathlib.Path('/mnt/c/Users/Breez/.gemini/antigravity/mcp_config.json'); d=json.loads(p.read_text()); d['mcpServers']['twin-memory']['headers']['X-TP3-MCP-TOKEN']='7ee7f2f28744847727023cab0147749c83172018bfea0cd6fed6589a4d42fc6b'; p.write_text(json.dumps(d,indent=2))"

After running, fully quit and relaunch Antigravity (the MCP client only re-reads the file at startup), then check the Antigravity MCP panel for twin-memory showing green / connected.

What was NOT done (per instructions)