Repository navigation
feat(mcp): an MCP server credential may be an OAuth token - #20
Merged
Merged
Conversation
TheGreatAxios
force-pushed
the
cl-9631-mcp-credential-may-be-oauth-token
branch
from
September 30, 2026 20:18
65ee8d6 to
38fdde1
Compare
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.
Discovery accepts an
oauth_tokencredential as the bearer source alongsideapi_key; other types (certificate, other) now read as not found.The secret is the current access token, which oauth-core's refresher rewrites in place, so no refresh logic is added here.
The runtime bundle is unchanged: the credential provider already shapes the handle from the current secret.
README documents
metadata.mcp.auth(none, token, oauth); tests cover an oauth_token row and lapsed or non-bearer rows.Resolves CL-9631