fix(mcp): use correct authorization server URL for OAuth discovery #7234
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.
Summary
Upgrade
@modelcontextprotocol/sdkfrom 1.15.1 to 1.25.2 to fix OAuth discovery for external authorization servers.Fixes #7228
Problem
When an MCP server's protected resource metadata returns an external
authorization_serversURL (e.g., Auth0), OpenCode incorrectly fetches/.well-known/oauth-authorization-serverfrom the MCP server instead of the authorization server.Solution
Upgrade the MCP SDK to 1.25.2, which fixes the URL construction in
discoverOAuthMetadata().Related
PR #5940 addresses the same SDK bug but also adds a
redirectUriconfiguration option. This PR is a minimal fix focusing only on the SDK upgrade. TheredirectUrifeature could be considered separately.