Advertise dev OAuth issuer from MCP discovery - #211
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
masnwilliams
approved these changes
Sep 22, 2026
masnwilliams
left a comment
masnwilliams
left a comment
Collaborator
There was a problem hiding this comment.
Reviewed the discovery mapping and tests. The dev issuer selection is contained in the existing discovery module, preserves production and other host behavior, and introduces no structural quality regression.
This branch was successfully deployed
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
2 participants
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
Route dev MCP OAuth discovery to the canonical dev authorization server after the auth hostname moved to the staging API. Preserve the resource identity and the existing production mapping; other preview and local hosts continue to use their own origins.
Cover direct requests, requests routed through Next with a public Host, near-match hostnames, and the HTTP discovery route.
Validation
bun test— 664 passed.AGENTS.mdformatting).This PR changes metadata only; it does not deploy or modify the authorization server.