Higgsfield MCP is moving client identification from Dynamic Client Registration (DCR) to Client ID Metadata Documents (CIMD). DCR is switched off on January 1, 2027, and CIMD becomes the only way for a third-party client to identify itself. Developers whose MCP client registers through DCR must migrate before that date. People who use an MCP client built by someone else have nothing to configure on the Higgsfield side.
What Is Changing?
Both methods work now. Only the way a client identifies itself to https://mcp.higgsfield.ai/mcp changes. The rest of the OAuth flow stays the same.
Date | DCR | CIMD |
|---|---|---|
Now | Supported | Supported |
Until December 31, 2026 | Supported, deprecated | Supported, recommended |
From January 1, 2027 | Switched off | Required |
From January 1, 2027, the registration endpoint stops accepting requests, and client IDs issued through DCR stop working.
Who Is Affected?
Any MCP client that obtains its client_id by calling the registration endpoint. To check, look at the client's network traffic during the first authorization. A POST to the registration endpoint means the client uses DCR and has to migrate.
Clients that already send an HTTPS metadata document URL as client_id are not affected.
People who use an MCP client built by someone else don't need to configure anything on the Higgsfield side. CIMD support depends on that client, so they should keep it up to date.
How Is CIMD Different From DCR?
With DCR, a client sends a registration request, and the authorization server issues a client_id and stores it. With CIMD, the client_id is an HTTPS URL that the developer controls, and the authorization server reads the client metadata from that URL.
Criteria | DCR | CIMD |
|---|---|---|
| Opaque string issued by the server | HTTPS URL of the metadata document |
Registration request | Required for every installation | None |
Where metadata lives | On the authorization server | On the developer's domain |
Updating metadata | Re-register | Edit the document |
Identity | Unverified, anyone can register any name | Tied to a domain the developer controls |
Client secret | Optional | None, public client with PKCE |
How Do Developers Migrate?
- Create the metadata document (see the next section).
- Host it at a stable public HTTPS URL on a domain under the developer's control. This URL is the
client_id. - In the client, check that the authorization server metadata shows
client_id_metadata_document_supportedastrue. - Skip the registration call. Send the document URL as
client_idin the authorization request and in the token request. - Keep everything else as is: authorization code flow, PKCE with
S256, theresourceparameter, and refresh tokens. - Remove the DCR code path and any stored DCR
client_idvalues before January 1, 2027.
For a client that uses an official MCP SDK, update to a version that supports CIMD and pass the document URL in the client configuration.
