MCP authorisation

The part of the MCP specification that protects remote servers with OAuth: the server acts as a resource server and accepts only bearer tokens issued for it.

In more detail

A request without a valid token gets 401 with a WWW-Authenticate header pointing to the server's protected resource metadata. The client runs an authorisation code flow with PKCE naming the server as the resource, identifying itself with a Client ID Metadata Document now that dynamic registration is deprecated. The server must never pass the token on to another API.

Related terms

Taught in

References

Certification courses