By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

MCP authorization

The MCP specification defines how HTTP based servers protect themselves with OAuth: the server acts as a resource server, points clients to its authorization server, and accepts only tokens issued for it. Local stdio servers sit outside this model and usually take credentials from the environment. Knowing which servers follow which model is the first step in any token review.

Read in this order

  1. OfficialUnderstanding authorization in MCPStart here: a guided walk through how MCP authorization fits together.
  2. VideoIntro to OAuth for MCP Servers (MCP Developers Summit 2025)Connects OAuth concepts to MCP server implementation. 19 min.
  3. ArticleLet's fix OAuth in MCP (Aaron Parecki)An OAuth expert explains why the resource server and authorization server roles were split.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.