Choose one resource
Register the API or MCP server the client is asking to reach—not the user’s entire account.
MCP AuthorizationAvailable now
Don’t give an AI client the user’s whole session.
Let the user approve one protected resource and a defined set of actions. Issue the client a short-lived token for that audience, then verify it at your MCP server or API.
Approve specific actions
Ask for explicit scopes and preserve the grant instead of handing the client a broad credential.
Enforce at the resource
Validate issuer, signature, audience, expiry, and scope before your server performs the action.
Product scope
One resource. Explicit actions. A short expiry.
MCP Authorization protects MCP servers and APIs you own. Connecting your own agents out to an account someone else owns is the other direction — that is Agent Access, with its own page. Sender-constrained (DPoP) tokens are still roadmap work.
- Resource metadata and challenge values generated for you (RFC 9728)
- Environment-scoped resource servers
- Explicit scopes and grants
- Resource-aware authorization requests
- 15-minute audience-bound signed access tokens
- Consent and grant audit evidence
Available now