MCP auth: Stop registering, Start linking

Microsoft Developer explains why Dynamic Client Registration becomes a scaling problem for MCP clients, and how switching to Client ID Metadata Documents turns the client_id into a durable, URL-based identity that servers can fetch on demand.

Overview

The video focuses on authentication for MCP clients and servers, highlighting a practical issue with Dynamic Client Registration (DCR): when a client meets many servers (especially opportunistically), DCR can cause the client to mint a new client_id per server, creating a per-server credential burden that does not scale well.

It then introduces an alternative approach using Client ID Metadata Documents, which flips the model:

• Instead of treating client_id as a server-issued identifier that changes per server, the client_id becomes a URL.
• A server can fetch the client’s metadata on demand from that URL.
• This enables a single durable client identity that can work across servers.

The session includes a live demonstration of the end-to-end flow using this URL-based client_id + metadata document approach.