Skip to main content
Use oauthAuth0Provider when Auth0 is the authorization server. MCP clients register directly with Auth0, and mcp-use verifies Auth0 access tokens against the resolved MCP resource.

Configure Auth0

In the Auth0 Dashboard:
  1. Enable the Resource Parameter Compatibility Profile.
  2. Promote the login connections MCP clients may use to domain-level connections.
  3. Create an API whose identifier is the canonical MCP resource, such as https://mcp.example.com/mcp.
  4. Use the rfc9068_profile_authz token dialect if tools need Auth0 permissions in access tokens.
The API identifier must match the resource that mcp-use resolves for token verification. Auth0 provider options do not include a separate audience.

Configure the server

Treat the environment variable as application configuration and pass domain explicitly.

Use Auth0 identity and permissions

Auth0 normalizes the subject to ctx.auth.user.id. It also maps optional email, name, nickname, picture, emailVerified, and updatedAt fields plus roles. Token permissions are available at top-level ctx.auth.permissions.

Verify the setup

Confirm that the client registers with Auth0, the token audience is the resolved MCP resource, invalid tokens are rejected, and permission-protected tools reject callers without the required permission.

Runnable Auth0 example

Compare with the maintained Auth0 example.

Auth0 MCP Authorization Guide

Configure Auth0 for MCP authorization.

User Context

Use normalized Auth0 identity and permissions.