mcp

GET /.well-known/oauth-authorization-server

OAuth 2.1 authorization-server metadata for AI apps (RFC 8414).

All mcp endpoints

All developer docs →

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/.well-known/oauth-authorization-server

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

The engine's own authorization server for MCP clients (Claude, ChatGPT, Cursor…): dynamic client registration (RFC 7591), Client ID Metadata Documents, PKCE S256 only, rotating refresh tokens and RFC 7009 revocation. The person signs in through Keycloak on the dashboard consent page and picks the organization and permissions the app gets (docs/27 §3a). 404 while the OAuth kill switch is off. Unauthenticated.

Response

NameTypeRequiredWhat it is
issuerstringYes—
authorization_endpointstringYes—
token_endpointstringYes—
registration_endpointstringNo—
revocation_endpointstringNo—
response_types_supportedstring[]Yes—
response_modes_supportedstring[]No—
grant_types_supportedstring[]No—
code_challenge_methods_supportedstring[]Yes—
token_endpoint_auth_methods_supportedstring[]No—
revocation_endpoint_auth_methods_supportedstring[]No—
client_id_metadata_document_supportedbooleanNo—
authorization_response_iss_parameter_supportedbooleanNo—
scopes_supportedstring[]No—
service_documentationstringNo—
op_policy_uristringNo—
op_tos_uristringNo—

Errors this endpoint can return

404