OAuth authorization
MCP uses OAuth 2.1 Authorization Code with PKCE. Clients must not use channel secrets directly or write access tokens to logs or persistent storage.
Endpoints
| Endpoint | Method | Purpose |
|---|---|---|
/services/oauth/authorize |
GET |
Start authorization |
/services/oauth/token |
POST |
Exchange an authorization code for an access token |
/services/oauth/revoke |
POST |
Revoke a token |
/services/oauth/register |
POST |
Dynamically register a public client when enabled for the environment |
The protected resource metadata returns the actual authorization server and resource identifier. Prefer discovery over hard-coding an environment domain.
Authorization requirements
- Use
response_type=code. - Use
code_challenge_method=S256. redirect_urimust match the registered client. Loopback clients should use the dynamic port rules from OAuth.- Requested scopes must be supported MCP scopes.
- Requests to
/services/mcpmust useAuthorization: Bearer.
Scopes
Public tool scopes:
mcp:hotel.meta.search
mcp:hotel.search
mcp:hotel.rates
mcp:hotel.rate-rule
mcp:order.search
Internal analysis tools require an additional account capability. A tool is not exposed or callable when either the token scope or account capability is missing.