---
title: "Oauth Authorization Server Aggregate"
method: GET
path: "/.well-known/oauth-authorization-server/mcp"
tags: ["mcp"]
---

# Oauth Authorization Server Aggregate

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

OAuth authorization server discovery for the aggregate /mcp endpoint, the RFC 8414
path-inserted form for a client that treats {base}/mcp as its authorization base URL.

The single-segment /mcp is reserved for the aggregate so the discovery chain stays
consistent: the aggregate protected-resource document advertises {base}/mcp as its
authorization server, so the document served here must have issuer {base}/mcp. A server
literally named ``mcp`` therefore does not take this route; it keeps its standard
two-segment discovery at /.well-known/oauth-authorization-server/mcp/mcp. Letting the
per-server row win here instead would serve an issuer of {base} against a resource that
advertised {base}/mcp, which fails the RFC 8414 issuer check and breaks the front door.

## Response `200`

Successful Response

- unknown

## Changes

- **2026-09-21** `6246f8d427b7` — 2 info
  - api tag `mcp` added
  - api tag `mcp_byok_oauth` removed
- **2026-09-20** `3b2b241e4b0b` — 2 info
  - api tag `mcp_byok_oauth` added
  - api tag `mcp` removed
- **2026-09-18** `082b5fabd909` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/flock/apis/litellm-api/changes/.well-known/oauth-authorization-server/mcp/get.md)

---

[API](https://skmtc.dev/flock/apis/litellm-api.md) · [All operations](https://skmtc.dev/flock/apis/litellm-api/llms.txt) · [OpenAPI document](https://skmtc.dev/flock/apis/litellm-api/revisions/c71315002afa?raw)