Register an OAuth client
Dynamic client registration (RFC 7591). An MCP client registers itself before its first authorization request, so nobody has to add it by hand. This endpoint requires no authentication. Every client registered here is public: it holds no secret and proves itself on each authorization with PKCE, so registering grants nothing on its own — the user’s consent is still required. Each redirect_uri must use https, or http on a loopback address, and must not contain a fragment. Registration is rate-limited to 10 requests per hour per IP address. Fields a client sends that are not listed here are ignored.
Body
A display name for the client.
1 - 128Where to send the user back after authorization. An http loopback redirect URI matches a registered redirect URI on any port, per RFC 8252 section 7.3.
1 - 5 elements1024none authorization_code, refresh_token code