You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Serve OAuth protected resource metadata on the MCP server
The bearer-auth middleware already advertises a resource_metadata URL
in 401 WWW-Authenticate headers, but no route served it, so
spec-compliant clients following the pointer got a 404 (#22). In
EXTERNAL mode there was no way to discover the authorization server
at all besides the legacy RFC 8414 shim.
- Serve RFC 9728 protected resource metadata at
/.well-known/oauth-protected-resource (the URL advertised in 401s)
and /.well-known/oauth-protected-resource/mcp (RFC 9728 path
insertion), listing the mode-appropriate authorization server
- Keep the legacy /.well-known/oauth-authorization-server shim for
clients of the 2025-03-26 spec revision, and label it as such
Fixes#22
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0 commit comments