Refactor out Route generation for metadata endpoints #44
Conversation
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
Refactors the `auth_metadata_mount` function into it's component parts, so that consumer that need more flexibility can use lower level constructs. Namely, if you need to manually build the various OAuth metadata endpoints because your clients are non-standards compliant.
mnoble
force-pushed
the
matte/greater-metadata-control
branch
from
9c367cd to
c24b832
Compare
kamil-keycard
approved these changes
Dec 18, 2025
| service. | ||
|
|
||
| ``` | ||
| /.well-known/oauth-authorization-server |
Collaborator
There was a problem hiding this comment.
refer to oauth-protected-resource. This is what developers of MCP servers should be concerned with as "resource" servers.
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.
Gives greater control over where the OAuth metadata endpoints are mounted – particularly when using FastAPI + FastMCP, since that combo often results in non-standards compliance depending on how you're using them.
This is mostly for special cases where folks are building (usually internal) tools that don't abide by the OAuth spec and expect this data to be exposed at some custom URI.