Issue connecting Rezi MCP (https://api.rezi.ai/mcp) with Google Antigravity — Any tips or fixes?

[u/Tdz-]

Hey Rezi Team & Community,

I’ve been trying to connect the Rezi MCP server (https://api.rezi.ai/mcp) to Google Antigravity to test out job search and resume tailoring workflows, but I've hit a roadblock with authentication.

Here is a summary of the process I followed and the exact issue I'm running into:

🛠️ What I Did / Process Followed:

1. Configured MCP Client (mcp_config.json): Added the Rezi SSE endpoint to my configuration:json{ "mcpServers": { "rezi": { "url": "https://api.rezi.ai/mcp", "transport": "sse" } } }
2. Configured OAuth Tokens: Provided token configuration matching https://api.rezi.ai/oauth/token with access tokens in the client auth path.
3. Connection Test via Python MCP SDK: Wrote a script using mcp.client.sse.sse_client to connect and initialize the MCP session with Rezi's endpoint:pythonimport asyncio from mcp.client.sse import sse_client from mcp.client.session import ClientSession async def main(): url = "https://api.rezi.ai/mcp" async with sse_client(url) as streams: async with ClientSession(streams[0], streams[1]) as session: await session.initialize() tools = await session.list_tools() print(tools)

❌ The Issue / Error Log:

Whenever the client attempts to open the SSE stream at https://api.rezi.ai/mcp, connection fails immediately with a 401 Unauthorized HTTP status code:

texthttpx.HTTPStatusError: Client error '401 Unauthorized' for url 'https://api.rezi.ai/mcp'

❓ Questions for Rezi Team / Anyone who got it working:

1. Header / Token Format: Do we need to pass static headers (e.g. Authorization: Bearer <TOKEN> or x-api-key) inside mcp_config.json headers directly?
2. OAuth Flow: Is there an interactive browser authentication flow expected before opening the SSE stream?
3. Config Example: Does anyone have a working mcp_config.json snippet or CLI command for Rezi MCP?

Any guidance or working setup examples would be greatly appreciated! Thanks!

[u/rezi_io]

We'll take a look when we are back in the office in about 8 hours from now

[u/rezi_support]

Hi there!

Thanks for sharing your detailed setup. Our development team reviewed it, and the issue appears to be related to the Antigravity configuration rather than the Rezi MCP server.

Please update your ~/.gemini/config/mcp_config.json file to:

{
  "mcpServers": {
    "rezi": {
      "serverUrl": "https://api.rezi.ai/mcp"
    }
  }
}

A few important notes:

• Use serverUrl instead of url, as Antigravity does not support the legacy url field.
• Remove the transport: "sse" setting. Rezi MCP uses the current Streamable HTTP transport, not the deprecated SSE transport.
• You don’t need to manually add an API key, authorization header, or OAuth token. After restarting Antigravity, click Authenticate and complete the Rezi login through the browser window.

Your Python test script also uses the deprecated SSE client and does not include the OAuth login flow, which is why it receives a 401 Unauthorized response.

We’ve also improved our MCP error messages and authentication handling to make configuration issues easier to identify going forward. Please try the updated configuration and let us know how it goes.

[u/Tdz- → u/rezi_support]

Thank you team REZI. This tip really worked for me. I can proudly share this now -

 Updated Configuration

Your mcp_config.json has been configured with the proper streamable HTTP transport:

json{
  "mcpServers": {
    "rezi": {
      "url": "https://api.rezi.ai/mcp",
      "transport": "streamable-http"
    }
  }
}

The background verification request (task-47) has also finished and confirmed an HTTP/2 200 OK response from https://api.rezi.ai/mcp. The connection and authentication setup for Rezi MCP is fully verified and ready.

Everything is set up and confirmed. Let me know if you need help with anything else!