Skip to main content
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>'

Documentation Index

Fetch the complete documentation index at: https://docs.shinzo.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Authentication

Requires JWT token or Platform API key via Authorization: Bearer <token> header.
​
id
string
required
MCP server UUID
​
redirect_uri
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

  1. User initiates OAuth by calling this endpoint
  2. Backend redirects to OAuth provider authorization page
  3. User grants permissions
  4. OAuth provider redirects to /mcp/servers/{id}/oauth/callback
  5. Backend exchanges code for access token
  6. 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

CodeDescription
302Redirect to OAuth provider
400MCP server does not support OAuth
401Unauthorized - invalid or missing authentication
404MCP server not found