New in version: 2.12.4
OIDC Proxy enables FastMCP servers to authenticate with OIDC providers that don’t support Dynamic Client Registration (DCR) out of the box. This includes OAuth providers like: Auth0, Google, Azure, AWS, etc. For providers that do support DCR (like WorkOS AuthKit), use RemoteAuthProvider
instead.
The OIDC Proxy is built upon OAuthProxy
so it has all the same functionality under the covers.
Implementation
Provider Setup Requirements
Before using OIDC Proxy, you need to register your application with your OAuth provider:- Register your application in the provider’s developer console (Auth0 Applications, Google Cloud Console, Azure Portal, etc.)
- Configure the redirect URI as your FastMCP server URL plus your chosen callback path:
- Default:
https://your-server.com/auth/callback
- Custom:
https://your-server.com/your/custom/path
(if you setredirect_path
) - Development:
http://localhost:8000/auth/callback
- Default:
- Obtain your credentials: Client ID and Client Secret
The redirect URI you configure with your provider must exactly match your
FastMCP server’s URL plus the callback path. If you customize
redirect_path
in OAuth Proxy, update your provider’s redirect URI accordingly.Basic Setup
Here’s how to implement OIDC Proxy with any provider:Configuration Parameters
OIDCProxy Parameters
URL of your OAuth provider’s OIDC configuration
Client ID from your registered OAuth application
Client secret from your registered OAuth application
Public URL of your FastMCP server (e.g.,
https://your-server.com
)Strict flag for configuration validation. When True, requires all OIDC
mandatory fields.
Audience parameter for OIDC providers that require it (e.g., Auth0). This is
typically your API identifier.
HTTP request timeout in seconds for fetching OIDC configuration
JWT algorithm to use for token verification (e.g., “RS256”). If not specified,
uses the provider’s default.
List of OAuth scopes to request from the provider. These are automatically
included in authorization requests.
Path for OAuth callbacks. Must match the redirect URI configured in your OAuth
application
List of allowed redirect URI patterns for MCP clients. Patterns support wildcards (e.g.,
"http://localhost:*"
, "https://*.example.com/*"
).None
(default): All redirect URIs allowed (for MCP/DCR compatibility)- Empty list
[]
: No redirect URIs allowed - Custom list: Only matching patterns allowed
Token endpoint authentication method for the upstream OAuth server. Controls how the proxy authenticates when exchanging authorization codes and refresh tokens with the upstream provider.
"client_secret_basic"
: Send credentials in Authorization header (most common)"client_secret_post"
: Send credentials in request body (required by some providers)"none"
: No authentication (for public clients)None
(default): Uses authlib’s default (typically"client_secret_basic"
)
Storage backend for persisting OAuth client registrations. By default, clients are automatically persisted to disk in
~/.config/fastmcp/oidc-proxy-clients/
, allowing them to survive server restarts as long as the filesystem remains accessible. This means MCP clients only need to register once and can reconnect seamlessly after your server restarts.Using Built-in Providers
FastMCP includes pre-configured OIDC providers for common services:Auth0Provider
at present.
Scope Configuration
OAuth scopes are configured withrequired_scopes
to automatically request the permissions your application needs.
Dynamic clients created by the proxy will automatically include these scopes in their authorization requests.
Environment Configuration
New in version: 2.13.0
For production deployments, configure OIDC Proxy through environment variables instead of hardcoding credentials: