Creator Hub
Back

Higgsfield MCP Moves to CIMD: What Developers Need to Know

Higgsfield
4 min
Higgsfield MCP Moves to CIMD: What Developers Need to Know

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.

What Is Changing?

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.

How Is CIMD Different From DCR?

Criteria

DCR

CIMD

client_id

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?

  1. Create the metadata document (see the next section).
  2. Host it at a stable public HTTPS URL on a domain under the developer's control. This URL is the client_id.
  3. In the client, check that the authorization server metadata shows client_id_metadata_document_supported as true.
  4. Skip the registration call. Send the document URL as client_id in the authorization request and in the token request.
  5. Keep everything else as is: authorization code flow, PKCE with S256, the resource parameter, and refresh tokens.
  6. Remove the DCR code path and any stored DCR client_id values 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.

What Goes Into the Metadata Document?

  • client_id must match the document URL exactly, character for character.
  • client_name is shown to the user on the consent screen.
  • redirect_uris lists every redirect URI the client uses. Matching is exact.
  • The URL uses https and has a path. It has no fragment, no credentials, and no . or .. path segments.
  • The document is publicly reachable without authentication and returns 200 with Content-Type: application/json.
  • The URL is stable. Changing it creates a new client, and every user has to authorize again.

What Happens to Users After the Switch?

Switching from a DCR client_id to a CIMD client_id creates a new client from the authorization server's point of view. Tokens issued to the old client_id don't carry over, so each user signs in and authorizes once after the developer ships the change. Their Higgsfield account, credits, and Assets aren't affected.

How Can Developers Verify the Migration?

  1. Fetch the document URL from outside the developer's network. It should return 200, JSON, and a client_id equal to the URL.
  2. Run a full authorization with a clean client state and no stored DCR credentials.
  3. Confirm that no request goes to the registration endpoint and that the consent screen shows the client_name.

Got any questions left?

by Higgsfield