mcp
GET /.well-known/oauth-authorization-server/v1/mcp
The authorization-server metadata, for clients that append the resource path.
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/v1/mcpSigned 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
Identical to /.well-known/oauth-authorization-server. Unauthenticated.
Response
| Name | Type | Required | What it is |
|---|---|---|---|
issuer | string | Yes | — |
authorization_endpoint | string | Yes | — |
token_endpoint | string | Yes | — |
registration_endpoint | string | No | — |
revocation_endpoint | string | No | — |
response_types_supported | string[] | Yes | — |
response_modes_supported | string[] | No | — |
grant_types_supported | string[] | No | — |
code_challenge_methods_supported | string[] | Yes | — |
token_endpoint_auth_methods_supported | string[] | No | — |
revocation_endpoint_auth_methods_supported | string[] | No | — |
client_id_metadata_document_supported | boolean | No | — |
authorization_response_iss_parameter_supported | boolean | No | — |
scopes_supported | string[] | No | — |
service_documentation | string | No | — |
op_policy_uri | string | No | — |
op_tos_uri | string | No | — |
Errors this endpoint can return
404