Customizing .well-known/oauth-authorization-server

[sergeev0]

I am trying to integrate my FastMCP server with my Keycloak for Oauth. The idea is that my underlying backend requires user authentication to get the data, so MCP server need to require a token and pass it to the backend for auth. The problem I am facing currently is that FastMCP creates .well-known/oauth-authorization-server and it does not include crucial data clients need to do dynamic client registration (i.e. correct registration endpoint). Any way I can customize that?

[bojanbg]

Can you share your code? When I use client_registration_options=ClientRegistrationOptions(enabled=True) in the OAuthProvider constructor, I do see the client registration endpoint added. However, I have other issues that are preventing me from giving a complete working example.

[sergeev0]

I am sorry, I already deleted this code and resorted to using local MCP server instead with remote API as I realized that is something that the current ecosystem is more adapted to in general as opposed to remote MCP server.
The problem was either with /register URL not included or my inability to customize it to my Keycloak's correct register URL.
Sorry if I wasted any of your time.

[bojanbg]

No need to apologize, thank you for the follow up.