[MCP Store] Update Supabase MCP listing to use remote server

Google Antigravity
,
1

Hi Antigravity team/community,

I’m a member of the team that maintains the Supabase MCP Server. We’ve recently observed a large volume of traffic from Antigravity IDE though our [legacy stdio MCP package npmjs. com /package/ @supabase/mcp-server-supabase, likely due to Antigravity’s MCP Store using this configuration for the Supabase listing. We currently recommend clients connect via our [remote MCP server supabase. com/ blog/remote-mcp-server instead. This allows authentication through our OAuth server instead of manually/unsafely adding Personal Access Tokens to the MCP config file.

While Antigravity doesn’t currently seem capable of connecting natively to our remote MCP server with OAuth (tested with the "serverUrl” field), I’ve verified it’s possible to connect through the mcp-remote proxy package.

{
  "mcpServers": {
    "supabase": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.supabase.com/mcp"
      ]
    }
  }
}

What steps can we take to update the official Supabase listing to use this remote setup instead of the legacy package?

4

YES - please fix this - I just spent a week trying to get this system set up and it has been a nightmare. This is an easy fix and the native store does NOT have the right settings.

I just got this system to work by connecting with Vanilla VS Code and then using those same setting in the MCP file - I use ALL the IDEs and Claude Code and Google Antigravity has by far been the WORST with MCP server connections

Please fix your stuff Google Team

FYI this is the json script that worked:

{

“mcpServers”: {

“supabase”: {

“type”: “http”,

“url”: “https://mcp.supabase.com/mcp?project_ref=\[YOUR PROJECT ID HERE]”

},
5

We’ve updated the docs to show how to manually configure Antigravity to use Supabase remote MCP, see Model context protocol (MCP) | Supabase Docs

@Adora_Vale In my testing the Antigravity config uses "serverUrl”instead of "url” / "type”, e.g. in ~/.gemini/antigravity/mcp_config.json:

{
  "mcpServers": {
    "supabase": {
      "serverUrl": "https://mcp.supabase.com/mcp"
    }
  }
}
6

Hi @mattrossman-supabase ,

We apologies for the delay in getting back to you. Could you please let us know if you are still experiencing the issue?

7

Yes and it’s not just the Supabase MCP - I use Claude Code, Cursor, and Antigravity and the entire MCP system is much more difficult than it should be here in Antigravity.

8

recently while using the supabase mcp I am
Error: failed to get tools: calling “tools/list”: Failed to parse Supabase Content API response: [ { “code”: “invalid_union”, “errors”: [ [ { “code”: “invalid_type”, “expected”: “nonoptional”, “path”: [ “errors” ], “message”: “Invalid input: expected nonoptional, received undefined” } ], [ { “expected”: “undefined”, “code”: “invalid_type”, “path”: [ “data” ], “message”: “Invalid input: expected undefined, received object” }, { “expected”: “array”, “code”: “invalid_type”, “path”: [ “errors” ], “message”: “Invalid input: expected array, received undefined” } ] ], “path”: [], “message”: “Invalid input” } ].

changed the argument to https://mcp.supabase.com/mcp and it works. Is the issue caused from supabase end?

9

Thanks so much everyone for reporting. This has been fixed in v1.23.2 : Google Antigravity

Please update and take a look. Thank you.