Skip to content
AdminKit

OAuth 2.0 Dynamic Client Registration

What is OAuth 2.0 Dynamic Client Registration?

OAuth 2.0 Dynamic Client Registration, defined in RFC 7591, lets a client obtain its own client ID by posting metadata to an authorization server, instead of a developer provisioning credentials manually in advance. AdminKit's MCP server hardening checklist requires supporting it, since general-purpose clients meet unfamiliar servers constantly.

By AdminKit team, Netbase JSC · Updated

OAuth 2.0 Dynamic Client Registration, defined in RFC 7591 (current document status at its IETF Datatracker entry), lets a client obtain its own client ID, and optionally a client secret, by posting its metadata — redirect URIs, client name, requested grant types — directly to an authorization server’s registration endpoint, instead of a developer manually registering it through that server’s portal ahead of time. The full set of metadata fields a client can send is catalogued in IANA’s OAuth Dynamic Client Registration Metadata registry. This matters specifically for MCP, where a general-purpose client is expected to connect to servers, and their authorization servers, it has never encountered before; requiring every server operator and client developer to coordinate credentials in advance doesn’t scale to that many unplanned pairings, which is why the MCP authorization specification adopted dynamic registration rather than assuming out-of-band setup. The current revision of that specification makes dynamic registration optional (MAY) for MCP clients and authorization servers and marks it deprecated, kept for backwards compatibility with authorization servers that do not support Client ID Metadata Documents, which it now recommends instead. OpenID Connect has its own registration profile, OpenID Connect Dynamic Client Registration 1.0, which defines a client registration endpoint for relying parties and is also listed among the standards the MCP specification builds on. An authorization server can still require an initial access token to gate who’s allowed to register, or a signed software statement vouching for the client’s metadata — dynamic registration means the step doesn’t require a human in the loop, not that it’s unauthenticated. Where that registration endpoint actually lives is published in the authorization server’s own OAuth 2.0 Authorization Server Metadata, and a client obtained this way still goes through the same PKCE-protected authorization code flow as one registered manually — dynamic registration only changes how the client gets credentials, not how the authorization step itself is secured. A registered client can later update or deregister itself using the companion RFC 7592 management protocol, if the authorization server supports it.

OAuth 2.0 Dynamic Client Registration is part of AdminKit’s AI agents & MCP cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What problem does Dynamic Client Registration solve?

It lets a client obtain its own client ID by posting metadata directly to an authorization server, instead of a developer manually provisioning credentials in advance.

Does dynamic registration mean a client is unauthenticated?

No -- an authorization server can still require an initial access token or a signed software statement to gate who's allowed to register; it just removes the need for a human in the loop.

Why does MCP require Dynamic Client Registration?

Because a general-purpose MCP client is expected to connect to servers it has never encountered before, and coordinating credentials in advance doesn't scale to that many unplanned pairings.

Can a client registered this way update or remove its registration later?

Yes, using the companion RFC 7592 management protocol, if the authorization server supports it.