---
title: "Client ID Metadata Support for MCP Auth"
description: "WorkOS Connect now supports Client ID Metadata Document, or CIMD for use with MCP."
url: https://workos.com/changelog/client-id-metadata-support-for-mcp-auth
---

# Client ID Metadata Support for MCP Auth

WorkOS Connect now supports [Client ID Metadata Document](https://www.ietf.org/archive/id/draft-parecki-oauth-client-id-metadata-document-00.html), 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](https://workos.com/docs/reference/workos-connect/authorize), 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](mailto:support@workos.com) to get started.

MCP clients previously used [dynamic client registration](https://workos.com/docs/authkit/mcp/integrating/enabling-dynamic-client-registration) to identify themselves to WorkOS Connect, and Connect will continue to support DCR for clients that have not yet implemented CIMD.
