We use Google Gemini Enterprise (formerly Agentspace) and want to connect it to Retool as an MCP data connector. I couldn't find any forum posts or docs about this setup.
What I tried
I registered an OAuth client through Retool's dynamic client registration endpoint:
As expected, this returned a client ID and no client secret, because it's a public client.
In Gemini Enterprise, the authorization URL, token URL, client ID and redirect URI all point to the correct Retool OAuth endpoints for our org. The consent screen loads and I can approve the scopes, so the failure happens only when the authorization result is sent back to Gemini Enterprise.
The problem
After I approve the mcp:read / mcp:write scopes in Retool, the popup shows this message:
Couldn't finish connecting. Sign-in finished, but this window lost its connection to the page that opened it, so the authorization could not be passed back. Close this window. If this keeps happening, contact your administrator.
Questions
Has anyone connected Gemini Enterprise, or another Google Cloud connector, to Retool's MCP server?
Is this popup problem coming from Retool, for example a Cross-Origin-Opener-Policy header on the consent page that cuts the popup off from the page that opened it? Or is it on the Google side?
Does Gemini Enterprise need a confidential client with a client secret instead of a public client (token_endpoint_auth_method: none)? If so, can Retool issue one?
Any help or examples would be much appreciated. Thanks!
On a Cloud instance, an attempt to connect Google Gemini Enterprise (formerly Agentspace) to Retool's MCP server fails after approving the mcp:read/mcp:write scopes, with the popup showing 'Couldn't finish connecting⦠this window lost its connection to the page that opened it.' The question is whether this is a Retool-side popup/COOP issue, a Google-side issue, or whether a confidential client with a secret is required.
AI Response
Retool's MCP server documents and supports OAuth 2.0 connections only from specific coding-agent clients (Claude, ChatGPT/Codex, Cursor, Kiro, VS Code, and Retool Agents), each of which captures the OAuth callback itself; Google Gemini Enterprise is not a documented or supported client, and its popup-based redirect to vertexaisearch.cloud.google.com never receives the authorization result back from Retool's consent window. Separately, Retool support has confirmed that connecting to the MCP server via OAuth Dynamic Client Registration (RFC 7591) β the public, no-secret client flow used here β was not yet supported and has been shared with engineering, which is consistent with this failure. The reliable path today is to use one of the officially supported clients listed in the docs rather than a custom DCR public client; switching to a confidential client is not a documented option for this server.
Sources
Use Retool's MCP server | Retool Docs
Official guide listing the OAuth 2.0 connection details and the specific supported MCP clients (Claude, ChatGPT, Codex, Cursor, Kiro, VS Code, Retool Agents), none of which is Google Gemini Enterprise. Connecting to MCP via OAuth Dynamic Client Registration
Retool staff confirm that connecting to the MCP server via OAuth Dynamic Client Registration is not yet supported and was escalated to engineering β corroborating why the DCR-registered public client flow fails.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a , , or . Or by marking this post as the "Solution"! Let us know if you have any feedback here.
Thanks for making this post and reaching out via the Report a breakage form
We have released a fix that allows Google Gemini Enterprise to connect to Retool MCP.
We will document this officially soon, but to establish a connection from Gemini Enterprise to Retool MCP, you first need to log into your specific Retool instance using the browser that Gemini utilizes to complete the authentication process. This differs from using other LLM providers.