feat: use scopes_supported from resource metadata by default (fixes #580) #757
+114
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If available, all scopes in the field
scopes_supported
from/.well-known/oauth-protected-resource
are used by default in:Motivation and Context
See #580
How Has This Been Tested?
I tested this on a custom build of mcp-remote and it works well for the authorization endpoint
I didn't test DCR though because it's not available in my setup, but if you have a suggestion to test it I can do that too
Breaking Changes
It can technically be breaking since the default value is different
Types of changes
Checklist
Additional context