Skip to main content
GET
MCP OAuth Authorize

​
Authentication

Requires JWT token or Platform API key via Authorization: Bearer <token> header.
​
string
required
MCP server UUID
​
string
Optional redirect URI after OAuth completion

​
Example Request

​
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