MCP OAuth authentication does not send resource indicator (from RFC 8707)

API Bugs
1

When I try to connect a new custom MCP server, the resource parameter is not being sent to the authorization code grant URL.

e.g. it redirects to my URI (resource parameter is missing):
/oauth/authorize?response_type=code&client_id=***&redirect_uri=https%3A%2F%``2Fchatgpt.com``%2Fconnector_platform_oauth_redirect&state=oauth_s_***&code_challenge=***&code_challenge_method=S256

However according to the MCP specs the client MUST implement Resource Indicators from RFC 8707
see https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization#resource-parameter-implementation

Does anyone has the same issue?

2

I’m having the same issue, did you find a workaround?

3

Hey,

Our current authentication guide specifies that ChatGPT sends resource in both authorization and token requests, using the server identifier in its protected-resource metadata.

If this is still blocking your connection, contact support@openai.com for a closer look, keeping any configuration or logs private.

— Sanket