oauthClerkProvider when Clerk is the authorization server. MCP clients register directly with Clerk, and mcp-use verifies Clerk-issued access tokens.
Configure Clerk
In the Clerk Dashboard, enable Dynamic Client Registration for the application and copy its Frontend API URL. Enable and requestuser:org:read when tools need organization context.
Pass the Frontend API URL explicitly:
audience is optional. Set it only when Clerk emits that exact aud; when omitted, the provider uses issuer-bound access-token verification.
Use organization context
Clerk mapsorg_id, org_role, and org_slug to organizationId, organizationRole, and organizationSlug. Organization permissions are top-level ctx.auth.permissions.
id, optional email, name, username, picture, and emailVerified, plus roles.
Runnable Clerk example
Compare with the maintained Clerk example.
Clerk OAuth documentation
Review Clerk OAuth and DCR behavior.
User Context
Use Clerk identity, organization, and permissions.