MCP OAuth Authorize
curl --request GET \
--url https://api.app.shinzo.ai/v1/mcp/servers/{id}/oauth/authorize \
--header 'Authorization: Bearer <token>'MCP OAuth Authorize
Initiate OAuth flow for an MCP server requiring OAuth authentication.
GET
/
v1
/
mcp
/
servers
/
{id}
/
oauth
/
authorize
MCP OAuth Authorize
curl --request GET \
--url https://api.app.shinzo.ai/v1/mcp/servers/{id}/oauth/authorize \
--header 'Authorization: Bearer <token>'Authentication
Requires JWT token or Platform API key viaAuthorization: Bearer <token> header.
string
required
MCP server UUID
string
Optional redirect URI after OAuth completion
Example Request
curl "https://api.app.shinzo.ai/v1/mcp/servers/abc123/oauth/authorize?redirect_uri=https://myapp.com/callback" \
-H "Authorization: Bearer <token>"
Response
This endpoint returns a redirect response (HTTP 302) to the OAuth provider’s authorization page.Browser-Based Flow: This endpoint is designed for browser-based OAuth flows. It will redirect the user to the OAuth provider (e.g., Google, GitHub) for authorization. Not suitable for programmatic API access.
OAuth Flow
- User initiates OAuth by calling this endpoint
- Backend redirects to OAuth provider authorization page
- User grants permissions
- OAuth provider redirects to
/mcp/servers/{id}/oauth/callback - Backend exchanges code for access token
- MCP server is configured with OAuth credentials
Use Cases
Some MCP servers require OAuth authentication to access external services:- Google Cloud MCP: Requires Google OAuth to access GCP APIs
- GitHub MCP: Requires GitHub OAuth for repository access
- Slack MCP: Requires Slack OAuth for workspace access
Status Codes
| Code | Description |
|---|---|
302 | Redirect to OAuth provider |
400 | MCP server does not support OAuth |
401 | Unauthorized - invalid or missing authentication |
404 | MCP server not found |