Support for .well-known oauth discovery endpoints #132
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
This allows protecting a fastmcp server behind an oauth server.
This is done by adding support for OAuth 2.1 w A591 ell-known discovery endpoints to FastMCP, enabling MCP servers to serve OAuth metadata for authorization flows as required by MCP Specifications 2025-03-26 and 2025-06-18.
Note that additional features could be built on top of this like token verification, scope checks, and so on. This PR adds the minimum to allow mcp developers to add support for oauth auth.
Configuration