Repository navigation
docs: FTW Cloud now accepts Cursor's desktop OAuth callback - #2
Merged
Merged
Conversation
srcfl/ftw-cloud#53 is deployed: the exact cursor://anysphere.cursor-mcp/oauth/callback is accepted, other custom schemes are still refused.
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
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.
srcfl/ftw-cloud#53 is deployed to production (running sha256:13469dee…, built from 931e64b). Cursor's
cursor://anysphere.cursor-mcp/oauth/callbackis accepted byte for byte. Every other custom scheme is still refused, and PKCE S256 is still required. This updates the sign-in section of docs/SUBMISSION.md to match. The README doesn't mention callbacks, so it is unchanged.scripts/check.pypasses.