Register an OAuth client
RFC 7591 dynamic client registration, so MCP clients connect without anyone copying keys. Unauthenticated and rate-limited per IP. Registering grants nothing: a person must still approve the client for an agent.
Error codes: parameter_invalid, parameter_missing, rate_limited.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Optional client correlation id, up to 128 characters. It is not echoed: the response's X-Request-Id is always
our own req_… id. We log your value with the request as client_request_id, so support can find a request by
either id. A longer value is refused with 400 parameter_invalid.
128Body
RFC 7591 registration. Clients register themselves (no keys to copy). Only public clients with PKCE are accepted.
Shown on the consent page and in "Connected apps".
1 - 80Exact redirect URIs. Each must be https://, or http://localhost / http://127.0.0.1 with any port (native and CLI clients).
1 - 10 elementsDefaults to both.
authorization_code, refresh_token Defaults to ["code"].
code Must be none.
none Client home page.
Logo shown on the consent page (https only).
Space-separated scopes the client may later request.
Client software identifier.
200Client software version.
50Response
Client registered.
A registered OAuth client (RFC 7591 response).
Client id.
^cli_[0-9A-HJKMNP-TV-Z]{26}$Unix seconds.
Client name.
Registered redirect URIs.
Grants.
Response types.
Always none.
"none"Home page.
Logo.
Scopes registered.