Skip to content

Elicitation: clarify auth URL language in external OAuth guidance #1812

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pcarleton merged 1 commit into from
Nov 13, 2025
Merged

Elicitation: clarify auth URL language in external OAuth guidance #1812

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions docs/specification/draft/client/elicitation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -630,11 +630,12 @@ Credentials obtained via URL mode elicitation are distinct from the MCP server c
When implementing external authorization via URL mode elicitation:

1. The MCP server generates an authorization URL, acting as an OAuth client to the third-party service
2. The server creates a URL mode elicitation request with this URL
3. The user completes the OAuth flow directly with the third-party authorization server
4. The third-party authorization server redirects back to the MCP server
5. The MCP server securely stores the third-party tokens, bound to the user's identity
6. Future MCP requests can leverage these stored tokens for API access to the third-party resource server
2. The MCP server stores internal state that associates (binds) the elicitation request with the user's identity.
3. The MCP server sends a URL mode elicitation request to the client with a URL that can start the authorization flow.
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
Comment on lines +635 to +638

@nbarbettini nbarbettini Nov 13, 2025

Copy link
Copy Markdown
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)


The following is a non-normative example of how this pattern could be implemented:

Expand Down