Add OAuth PKCE login for HTTP MCP servers#4
Open
kuzaxak wants to merge 1 commit into
Open
Conversation
MCP servers such as LogDeck advertise OAuth metadata and expect clients to obtain their own bearer token instead of pasting one manually. The CLI only had a token-capture path, so a fresh configured HTTP server could not complete the standard authorization-code flow from auth login. Add protected-resource discovery, dynamic client registration, loopback callback handling, PKCE S256, resource-bound token exchange, and storage through the existing token store. Keep the explicit bearer-token paths intact for CI and servers that issue tokens out of band. Update the auth docs and protocol coverage so users can distinguish browser OAuth from direct bearer-token login, and document the remaining refresh/client-metadata gaps separately.
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
1 participant
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.
MCP servers such as LogDeck advertise OAuth metadata and expect clients to obtain their own bearer token instead of pasting one manually. The CLI only had a token-capture path, so a fresh configured HTTP server could not complete the standard authorization-code flow from auth login.
Add protected-resource discovery, dynamic client registration, loopback callback handling, PKCE S256, resource-bound token exchange, and storage through the existing token store. Keep the explicit bearer-token paths intact for CI and servers that issue tokens out of band.
Update the auth docs and protocol coverage so users can distinguish browser OAuth from direct bearer-token login, and document the remaining refresh/client-metadata gaps separately.