Uploaded December 2025 | Updated September 2026, 1 day ago
Modern AI tooling depends on standards, interoperability, and trust — but authentication has been one of the biggest friction points for teams adopting MCP in production.
In this talk, Den Delimarsky, Principal Product Engineer at Microsoft and MCP core maintainer, walks through a major evolution in MCP authentication: Client ID Metadata Documents.
This change removes the need for brittle Dynamic Client Registration (DCR) flows and replaces them with a simpler, standards-aligned model that works cleanly across tools like VS Code, MCP clients, and authorization servers.
What this talk covers
• Why Dynamic Client Registration became a bottleneck for MCP adoption
• How Client ID Metadata Documents work in practice
• What VS Code’s MCP support reveals about the future of authenticated tooling
• How authorization servers can reason about clients without manual registration
• What this unlocks for enterprise-grade MCP deployments
Why this matters for enterprise teams
As MCP adoption moves from experimentation to production, authentication can’t be:
• bespoke per tool
• fragile across environments
• or dependent on manual coordination
This approach enables:
• Predictable, inspectable auth flows
• Reduced integration risk
• Cleaner governance boundaries
• Faster adoption without sacrificing security
The MCP ecosystem — including maintainers, tool builders, and platform providers — is converging on patterns that scale. WorkOS is proud to support these standards as part of building the enterprise identity layer for modern AI infrastructure.
Modern AI tooling depends on standards, interoperability, and trust — but authentication has been one of the biggest friction points for teams adopting MCP in production.
In this talk, Den Delimarsky, Principal Product Engineer at Microsoft and MCP core maintainer, walks through a major evolution in MCP authentication: Client ID Metadata Documents.
This change removes the need for brittle Dynamic Client Registration (DCR) flows and replaces them with a simpler, standards-aligned model that works cleanly across tools like VS Code, MCP clients, and authorization servers.
What this talk covers
• Why Dynamic Client Registration became a bottleneck for MCP adoption
• How Client ID Metadata Documents work in practice
• What VS Code’s MCP support reveals about the future of authenticated tooling
• How authorization servers can reason about clients without manual registration
• What this unlocks for enterprise-grade MCP deployments
Why this matters for enterprise teams
As MCP adoption moves from experimentation to production, authentication can’t be:
• bespoke per tool
• fragile across environments
• or dependent on manual coordination
This approach enables:
• Predictable, inspectable auth flows
• Reduced integration risk
• Cleaner governance boundaries
• Faster adoption without sacrificing security
The MCP ecosystem — including maintainers, tool builders, and platform providers — is converging on patterns that scale. WorkOS is proud to support these standards as part of building the enterprise identity layer for modern AI infrastructure.
