Has anyone been able to get MCP connector working against Snowflake managed MCP servers? At first I was stuck at the OAuth configuration for the MCP connector in ChatGPT because it didn’t support specifying ClientID and ClientSecret, which Snowflake’s MCP servers require to use OAuth (they don’t support DCR). Then I noticed yesterday ChatGPT added the ability to specify Client ID and Secret. After trying that I get a little further. Setting up the MCP connector correctly forwards to the Snowflake login page. After authenticating on the Snowflake side (this required a work around because ChatGPT MCP connector does not allow you to specify a scope parameter), it redirects back to ChatGPT MCP connector setup and then errors out with a generic error. I tried several combinations and could not get it to work. I know this is all new on both sides, but I’m curious if anyone has gotten this to work.
Ran in to the same issues myself. Got through the Oauth config with the Snowflake docs but then when it gets passed back to chatGPT the error “Not all requested permissions were granted” shows up and the connector doesn’t work.
I use Auth0. It works well til Monday. From Tue, i also got “Not all requested permissions were granted” error like you.
Maybe ChatGPT update something and broken the OAuth?
Hi @rletness Do you mind sharing the workaround for the scope parameter?
Did you also need to whitelist any chatgpt egress IPs in snowflake?
The workaround was just to change the authorization URL based on this:
Change the scope from session%3Arole%3Aall to session%3Arole%3Arole name you want to authenticate and resubmit the URL.
This was taken from the Snowflake managed MCP server docs. The downside is that this has to be done each time you authenticate, which is not really a workaround, rather a big pain.
I talked to both Snowflake and OpenAI and it seems like the two sides (MCP client and MCP server) don’t quite speak the same protocol quite yet. Hopefully this is resolved soon.
See Apps SDK - it is showing the UI for a tool call, but not actually calling the tool - #4 by gusdeoliveira. I believe there was an update today that broke MCP apps.
Thanks. Yeah I tried that but it failed at the callback since the connector expects the all role scope. I have submitted a feature request too.