make client side client_id generation configurable in the oauth router#734
Merged
pcarleton merged 1 commit intomodelcontextprotocol:mainfrom Jul 14, 2025
Merged
Conversation
pcarleton
approved these changes
Jul 14, 2025
chenxi-null
pushed a commit
to chenxi-null/typescript-sdk
that referenced
this pull request
Jul 28, 2025
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
3 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.
Add the ability to toggle client side
client_idgeneration during the registration process.Motivation and Context
Some oauth servers will not let the client provide a
client_idduring registration and generate it themselves (eg. keycloak).Fixes #724
How Has This Been Tested?
I tested the entire flow with the MCP inspector and a production keycloak instance.
Breaking Changes
None.
Types of changes
Checklist
Additional context
None.