| Value | Meaning |
|---|---|
| preRegistered | Use pre-registered client information the client already has. |
| clientIdMetadataDocument | Use an OAuth Client ID Metadata Document (HTTPS-URL client_id). |
| dynamicClientRegistration | Fall back to Dynamic Client Registration (RFC 7591). |
| promptUser | Nothing applies — prompt the user to enter client information. |
The client-registration approach an MCP client should use for an authorization server, per the spec priority order ("Client Registration Approaches", 2025-11-25 / draft).