Fix #1430: Client Credentials providers scopes support (backported)#1442
Merged
pcarleton merged 3 commits intomodelcontextprotocol:v1.xfrom Feb 2, 2026
Merged
Conversation
|
commit: |
pcarleton
approved these changes
Feb 2, 2026
Member
pcarleton
left a comment
There was a problem hiding this comment.
Change looks good, i think it just needs linting
Author
|
Should I add a changeset, or is it something that is done by maintainers at release time? |
Member
|
we should fix that comment... changesets only matter for the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds support for a
scopeparameter in the client credentials OAuth providers as described in #1430.Motivation and Context
A client may now specify which scopes it requests to the Authorization Server.
How Has This Been Tested?
I have tested against an OAuth-compliant Authorization Server and an MCP Resource Server enforcing access control based on Access Token scopes.
Breaking Changes
No, the change is opt-in and the default behavior remains the same.
Types of changes
Checklist
Additional context
This is a backport of this feature to the
v1.xbranch, I'll open a similar PR against the upcoming v2 branch.