---
search:
  tags:
    - Operations
    - GET
seo:
  description: >-
    Returns the RFC 8414 authorization-server metadata… Reference for the GET
    /.well-known/oauth-authorization-server/mcp/chatgpt endpoint in the Charming
    API API.
sidebar:
  badge: GET
  label: OAuth authorization-server metadata for the ChatGPT MCP surface
title: OAuth authorization-server metadata for the ChatGPT MCP surface
type: openapi-operation
---
Returns the RFC 8414 authorization-server metadata for the `/mcp/chatgpt` surface, at the path-inserted well-known URL a client derives from an issuer carrying that path. Reached only when that surface's protected-resource document names the surface as its own authorization server, which `CHARMING__SERVER__CHATGPT_AUTH_PROXY_ADVERTISED` decides. The same switch decides whether this document is served, so the pointer and its target appear together: while it is off nothing names this URL and asking for it answers 404. Differs from the origin-wide document in `issuer`, which claims the surface, and in `authorization_endpoint`, which names the `usecharming.com` login proxy while the switch is on. Token, registration, and JWKS endpoints stay on this origin.

<Operation source="reference" id="get-oauth-authorization-server-mcp-chatgpt" />

Found a bug or need a feature? [Tell us](/docs/capabilities/feedback) with `submit_feedback` or `POST /app/{id}/feedback`. Your feedback shapes what we build next.