---
title: "OAuth 2.0 authorization server metadata (RFC 8414)"
method: GET
path: "/.well-known/oauth-authorization-server"
tags: ["discovery"]
---

# OAuth 2.0 authorization server metadata (RFC 8414)

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

## Request

- Base URL: `https://app.presify.io`
- URL: `https://app.presify.io/.well-known/oauth-authorization-server`
- Auth: none declared

Endpoints, grant types and PKCE methods of the Presify authorization server. The issuer is https://app.presify.io; the same document is served on the public website host for discovery convenience.

## Response `200`

Authorization server metadata.

- AuthorizationServerMetadata: RFC 8414 document.
  - `issuer` string, uri, required
  - `authorization_endpoint` string, uri, required
  - `token_endpoint` string, uri, required
  - `registration_endpoint` string, uri
  - `revocation_endpoint` string, uri
  - `response_types_supported` string[], required
  - `grant_types_supported` string[]
  - `code_challenge_methods_supported` string[]
  - `token_endpoint_auth_methods_supported` string[]
  - `revocation_endpoint_auth_methods_supported` string[]
  - `scopes_supported` string[]
  - `service_documentation` string, uri: Public setup guide for connecting an MCP client.
  - `client_id_metadata_document_supported` boolean: true when an https URL naming a Client ID Metadata Document is accepted as client_id (draft-ietf-oauth-client-id-metadata-document). Absent while the feature is switched off; dynamic client registration works either way.

---

[API](https://skmtc.dev/presify/apis/presify-public-api.md) · [All operations](https://skmtc.dev/presify/apis/presify-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/presify/apis/presify-public-api/revisions/5e3fe7801ad1?raw)