Higgsfield is moving its MCP server from Dynamic Client Registration (DCR) to Client ID Metadata Documents (CIMD), and developers using DCR must migrate before 1 January 2027. After that date, DCR-issued client IDs will stop working, so affected clients will lose their Higgsfield MCP connections until updated.
Higgsfield Watch analysis
What happened
Higgsfield says both methods work until 31 December 2026. CIMD becomes the only supported method from 1 January 2027, when the registration endpoint will stop accepting requests. The server address and the rest of the OAuth flow stay the same.
Developers can check whether their client uses DCR by looking for a POST to the registration endpoint during its first authorisation. To migrate, they need to host a public metadata document at a stable HTTPS URL on a domain they control, use that URL as the client ID, and confirm the authorisation server supports CIMD. They should remove the old registration call and stored DCR client IDs before the deadline. Higgsfield advises developers using an official MCP SDK to update to a version that supports CIMD.
The change means users will need to sign in and authorise the updated client once: tokens for the old client ID do not carry over. Higgsfield says users’ accounts, credits and Assets are unaffected. People using a third-party client do not need to change Higgsfield-side settings, but the client must support CIMD.
Why it matters
This is a real compatibility deadline for developers, not a change to MCP’s server address. Miss it and the client’s connection fails, which is the sort of calendar reminder nobody enjoys discovering through a broken workflow.
CIMD also changes who controls client identity. Instead of the server issuing and storing an ID after a registration request, the client uses a metadata URL controlled by its developer. Higgsfield says that identity is tied to the developer’s domain; the metadata document must be publicly reachable and its client ID must match its URL exactly.
Our read
There is time to migrate, and the OAuth flow itself stays put. Developers should check how their client obtains its ID now, test CIMD with a clean client state, and plan for users to authorise the new client once. Users of someone else’s client can leave the configuration to its developer, while keeping the client up to date. A deadline is much less dramatic when found in a changelog than in a failed login.
What to watch
- Whether MCP client SDKs add CIMD support ahead of the deadline.
- Whether developers complete migration and account for one-time user reauthorisation.
- Whether Higgsfield publishes further compatibility guidance as DCR’s shutdown approaches.
Discussion spark: Should MCP developers treat identity changes like this as a routine implementation detail, or should services provide a longer transition when users will need to authorise clients again?
Sources and evidence
- Source update (20 November 2026, 00:00 UTC)
Independent WittyWires tracker for public updates about Higgsfield. Not affiliated with or endorsed by Higgsfield; this is not an official account.