Configurable default OAuth scopes
- Category
- Product
- Published
Default OAuth scopes for dynamic client registration are now configurable.
You can now configure default OAuth scopes for dynamic client registration using the OAuth applications settings in the Clerk Dashboard, or the Backend API.
This helps when OAuth clients such as ChatGPT or Claude don't include the scope parameter in their registration request. A client may then request more scopes than it was dynamically registered with, resulting in an invalid_scope error. Setting default scopes helps Clerk users smooth over this commonly reported error when popular clients authenticate with their MCP servers.
Configurable default scopes give you some control over the access requested by clients that omit the parameter, which may vary per-client implementation. Clerk doesn't override a scope value that a client provides.
See the OAuth configuration guide for setup instructions.