Skip to content

Commit 2f533cc

Browse files
authored
Add priority word (modelcontextprotocol#1839)
1 parent d2b1364 commit 2f533cc

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/specification/draft/basic/authorization.mdx

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -203,6 +203,13 @@ MCP supports three client registration mechanisms. Choose based on your scenario
203203
- **Pre-registration**: When client and server have an existing relationship
204204
- **Dynamic Client Registration**: For backwards compatibility or specific requirements
205205

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+
206213
### Client ID Metadata Documents
207214

208215
MCP clients and authorization servers **SHOULD** support OAuth Client ID Metadata Documents as specified in

0 commit comments

Comments
 (0)