Table of contents
The running example
The three parties
One complete flow at a glance
Step 1: The client tries the MCP operation
Step 2: The client reads PRM
Step 3: The client reads authorization server metadata
Step 4: The client identifies itself — why CIMD matters
Step 5: The client prepares PKCE and asks for authorization
Step 6: The user signs in; the browser returns a code
Step 7: The client exchanges the code for a token
Step 8: The client retries the MCP request
Step 9: The MCP server validates authorization before executing
How this connects to the MCP protocol
What the client and server each store
Common misunderstandings and failure cases
Security checklist for the database server
The video example: what remains useful and what changed
A concise interview answer
Sources
How an AI client discovers a login provider, identifies itself with CIMD, obtains a resource-bound token, and calls protected MCP tools.
The running example
Imagine a company has a database and exposes a few…