You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/specification/draft/basic/authorization.mdx
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -203,6 +203,13 @@ MCP supports three client registration mechanisms. Choose based on your scenario
203
203
-**Pre-registration**: When client and server have an existing relationship
204
204
-**Dynamic Client Registration**: For backwards compatibility or specific requirements
205
205
206
+
Clients supporting all options **SHOULD** follow the following priority order:
207
+
208
+
1. Use pre-registered client information for the server if the client has it available
209
+
2. Use Client ID Metadata Documents if the Authorization Server indicates if the server supports it (via `client_id_metadata_document_supported` in OAuth Authorization Server Metadata)
210
+
3. Use Dynamic Client Registration as a fallback if the Authorization Server supports it (via `registration_endpoint` in OAuth Authorization Server Metadata)
211
+
4. Prompt the user if no other option is available
212
+
206
213
### Client ID Metadata Documents
207
214
208
215
MCP clients and authorization servers **SHOULD** support OAuth Client ID Metadata Documents as specified in
0 commit comments