Skip to content

Conversation

@nbarbettini
Copy link
Contributor

Motivation and Context

Follow-up to #887 to clarify some implementation guidance language.

How Has This Been Tested?

n/a

Breaking Changes

n/a

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

@nbarbettini nbarbettini changed the title Elicitation: clarify language on auth URL in external OAuth guidance Elicitation: clarify auth URL language in external OAuth guidance Nov 13, 2025
Comment on lines +635 to +638
4. The user completes the OAuth flow directly with the third-party authorization server
5. The third-party authorization server redirects back to the MCP server
6. The MCP server securely stores the third-party tokens, bound to the user's identity
7. Future MCP requests can leverage these stored tokens for API access to the third-party resource server
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(4 and below are unchanged)

@nbarbettini nbarbettini marked this pull request as ready for review November 13, 2025 15:21
@nbarbettini nbarbettini requested a review from a team as a code owner November 13, 2025 15:21
Copy link
Member

@pcarleton pcarleton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@pcarleton pcarleton merged commit 8e22f64 into modelcontextprotocol:main Nov 13, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants