OAuth 2.0 Protected Resource Metadata support

[hatasaki]

According to MCP atuhorization specification 2025-06-18, supporting OAuth 2.0 Protected Resource Metadata becomes MUST.
https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization

Do you have a plan to add /.well-known/oauth-protected-resource endpoint to response resource metadata and to add the resource server endpoint info to WWW-Authenticate header of MCP API endpoints?

[example RFC9728]
HTTP/1.1 200 OK
Content-Type: application/json

{
"resource":
"https://resource.example.com",
"authorization_servers":
["https://as1.example.com",
"https://as2.example.net"],
"bearer_methods_supported":
["header", "body"],
"scopes_supported":
["profile", "email", "phone"],
"resource_documentation":
"https://resource.example.com/resource_documentation.html"
}

[kamranayub]

It looks like this could be combined with the PRM support added here: https://github.com/blackchoey/remote-mcp-apim-oauth-prm

[Zambonilli]

Microsoft has released a labs that is based on blackchoey's example and have linked to this lab from the APIM MCP documentation.

If you only want to support MCP clients that respect RFC 9728 onwards, this lab seems like a better and more secure path forward than using this repo. You also don't have to self manage PKCE and this convoluted session token scheme that adds no real security benefits.

https://github.com/Azure-Samples/AI-Gateway/tree/main/labs/mcp-prm-oauth

[kamranayub]

I also have a secure MCP server fronted by Duende IdentityServer that supports PRM and DCR, all working with Aspire and Entra ID locally and hosted remotely on ACA. I built it as an alternative to APIM, since it works nicely for local demos and within Aspire.

That will be OSS alongside my existing Aspire MCP sample app over here:

https://github.com/kamranayub/pluralsight-course-mcp-in-practice