Hello,
It seems that when changing the MCP transport to the stateless version, ChatGPT apps stop working. Is this expected?
I can successfully add a Dev connector, but when starting to use it, inside the ChatGPT costumer chat, it triggers the “Auth” dialog, accepting, results in a loop, and reject it, in a failure.
The MCP does not have any authentication and I already validated that the tool can be called in the Chat development platform.
Thank you.
1 Like
I’ve suddenly been seeing the same thing today. We’ve been testing our app for weeks with no problems, now in the last week our App that does not require auth is getting us stuck in the Accept Connection dialog looping over and over again? Any ideas?
We are about to publish and this was REAL convenient timing for an issue like this to pop up
Posted in the other thread but wanted to post here as well and apologize for this experience - this was due to an internal caching issue that we identified and rolled back earlier today. The issue started yesterday morning and lasted until ~ 3pm today. It affected a portion of users that were attempting to authenticate/connect into their ChatGPT apps.
3 Likes
Thank you so much! Greatly appreciate the info - we are about to launch our app and were very worried there for a moment that something fundamentally changed in non-auth apps. Thanks for the transparency here and supporting the community.
thank you for the updates! 
1 Like
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.