Antigravity CLI can't connect to Figma's remote MCP server ("OAuth app with client id WPjiIBOlI6Snc0EeAjsit7 doesn't exist")

[Jesus_Ferreira]

Antigravity CLI (agy 1.4.3, Linux arm64) can’t authenticate with Figma’s remote MCP server (https//mcp.figma.com/mcp). After /mcp → Authenticate, Figma shows “OAuth app with client id WPjiIBOlI6Snc0EeAjsit7 doesn’t exist”, and the server never provides tools.

What’s known:

• Figma only lets the clients in its MCP catalog register, and Figma’s team has confirmed Antigravity isn’t one of them: https//forum.figma.com/suggest-a-feature-11/using-the-figma-remote-mcp-server-with-antigravity-cli-54916
• When the registration fails, agy falls back to a built-in client id that Figma doesn’t recognise.
• Other remote MCP servers (Notion, Supabase, Vercel, Wix) work fine in agy, and Codex CLI connects to Figma on the same machine.
• There’s a GitHub issue open since June, with 22+ upvotes and no reply yet: Bug: Figma MCP OAuth fails with "OAuth app with client id WPjiIBOlI6Snc0EeAjsit7 doesn't exist" · Issue #496 · google-antigravity/antigravity-cli · GitHub . I’ve also sent it through /feedback.

Could someone on the Antigravity team say whether Google is working with Figma to get Antigravity CLI into Figma’s MCP client catalog? Gemini CLI already has access, and Figma is one of the most used MCP servers for design work.

[Ambati_Rajendra]

Hi @Jesus_Ferreira,

Could you please share a few details to reproduce this issue:

• The reproduction steps to reproduce this issue?
• The Operating system you are using?

[Jesus_Ferreira]

Thanks for looking into it. Steps to reproduce:

1. Add Figma’s remote MCP server to ~/.gemini/config/mcp_config.json:
   “figma”: { “url”: “mcp.figma” }
2. Start agy and run /mcp.
3. Select the figma server and choose “Authenticate”.
4. The browser opens Figma’s authorization page, which shows:
   “OAuth app with client id WPjiIBOlI6Snc0E***** doesn’t exist”.
   The server never provides any tools.

Environment:

• Antigravity CLI 1.4.3 (also seen on 1.4.2)
• OS: ChromeOS with its Linux container (Debian 13 “trixie”), arm64
• The same happens on macOS arm64 according to GitHub issue #496, so it doesn’t look OS-specific.

For comparison, on the same machine and network, Codex CLI authenticates against mcp.figma without problems, and other remote MCP servers (Notion, Supabase, Wix) authenticate fine in agy.

[ERBAZXS111]

The comparison with Codex CLI on the same machine is useful. Since other remote MCP servers also authenticate correctly in agy, this looks much more like a Figma client-registration/OAuth compatibility issue than a general MCP transport problem. It would be useful to document which remote MCP providers require explicit client allowlisting.