Support Cursor OAuth client registration #895
Merged
+16
−16
Conversation
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
|
This will actually be really helpful! I just opened an issue for this #897. |
Kludex
approved these changes
Jun 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relaxes the restriction on
redirect_uriduring OAuth client registration (and token flows) fromAnyHttpUrltoAnyUrl.Motivation and Context
Cursor uses deeplinks with a custom scheme for
redirect_uriwhen registering OAuth clients for MCP, which currently fails validation (as it is not a validAnyHttpUrl).How Has This Been Tested?
Tested an MCP server using this branch and successfully registered Cursor as an OAuth client.
Breaking Changes
Types of changes
Checklist
Additional context