MCP Connector Creation Timeout - OAuth Callback Failing

Issue: Request timeout during MCP connector creation in ChatGPT App SDK

Details:

  • MCP server URL: hireboard-mcp-server-10315110388.us-central1.run.app/

  • Error: POST /backend-api/aip/connectors/links/oauth/callback returns 500 with {“detail”:“Request timeout”}

  • OAuth flow: Registration and authorization succeed, but token exchange times out

What works:

:white_check_mark: POST /backend-api/aip/connectors/mcp → 200 OK

:white_check_mark: POST /backend-api/aip/connectors/links/oauth → 200 OK

:white_check_mark: OAuth registration endpoint responds correctly

:white_check_mark: OAuth authorization endpoint responds correctly

:white_check_mark: Server logs show token endpoint receives requests

What fails:

:cross_mark: POST /backend-api/aip/connectors/links/oauth/callback → 500 Request timeout

:cross_mark: Token exchange appears to hang despite server responding quickly

Server Configuration:

  • Platform: Google Cloud Run

  • Cold start mitigation: min-instances=1, cpu-always-allocated=true

  • Timeout: 900s (15 minutes)

  • OAuth endpoints fully RFC 7591 compliant

  • Token endpoint supports application/x-www-form-urlencoded

  • Refresh token grant implemented

Request Payload:

{

“full_redirect_url”: "chatgpt.c**/connector_platform_oauth_redirect?code=…&state=…

}

Expected Behavior:

ChatGPT should exchange the authorization code for tokens via POST /oauth/token

Actual Behavior:

ChatGPT times out waiting for token exchange response, even though server logs show the request was received and processed quickly.

Additional Context:

This appears to be a platform-side timeout issue, as multiple developers have reported similar “Request timeout” errors during connector creation, particularly with OAuth flows. The server implementation follows all documented OAuth 2.0 and RFC 7591 requirements.

Please investigate the timeout behavior in the /oauth/callback flow.