Changelog

Client ID Metadata Support for MCP Auth

November 30, 2025

WorkOS Connect now supports Client ID Metadata Document, or CIMD for use with MCP.

MCP clients need a way to identify themselves to authorization servers without preregistration, and CIMD provides a secure way to do that. When clients redirect to the WorkOS Connect authorize endpoint, they provide a HTTPS URL as a client_id. WorkOS Connect reads the metadata served at that endpoint to identify the client and display a relevant consent screen to the end user. Contact us to get started.

MCP clients previously used dynamic client registration to identify themselves to WorkOS Connect, and Connect will continue to support DCR for clients that have not yet implemented CIMD.

This site uses cookies to improve your experience. Please accept the use of cookies on this site. You can review our cookie policy here and our privacy policy here. If you choose to refuse, functionality of this site will be limited.