API referenceM C P
Register a client dynamically (RFC 7591)
POST
A public client with its redirect URIs, good for thirty days of use. Clients with a metadata document need no registration.
application/json- body
client_name?stringredirect_uris*array<string>Registered
application/json- response
client_id*stringclient_name*stringredirect_uris*array<string>token_endpoint_auth_method*unknowngrant_types*array<string>response_types*array<string>curl -X POST 'http://127.0.0.1:7777/oauth/register' \ -H 'Content-Type: application/json' \ -d '{ "client_name": "My MCP client", "redirect_uris": [ "http://localhost:8765/callback" ]}'Example Response
{ "client_id": "string", "client_name": "string", "redirect_uris": [ "string" ], "token_endpoint_auth_method": "none", "grant_types": [ "string" ], "response_types": [ "string" ]}Exchange a code or a refresh token for tokens POST
`grant_type=authorization_code` (with `code`, `code_verifier`, `client_id`, `redirect_uri`, `resource`) or `grant_type=refresh_token` (with `refresh_token`, `client_id`; the refresh token rotates and a reuse revokes the family). Public clients (`token_endpoint_auth_method: none`).
Revoke an access or refresh token (RFC 7009) POST
Always 200. A refresh token takes its whole family with it.