Skip to main content
POST
MCP OAuth Callback

​
Authentication

Requires JWT token or Platform API key via Authorization: Bearer <token> header.
​
string
required
MCP server UUID
​
string
required
OAuth authorization code from provider
​
string
OAuth state parameter (for CSRF protection)

​
Example Request

​
Example Response

Internal Use: This endpoint is typically called automatically as part of the OAuth redirect flow initiated by OAuth Authorize. You rarely need to call it directly.

​
OAuth Flow

This endpoint is step 4 in the OAuth flow:
  1. User calls /mcp/servers/{id}/oauth/authorize
  2. OAuth provider shows authorization page
  3. User grants permissions
  4. Provider redirects here with authorization code ← This endpoint
  5. Backend exchanges code for access token
  6. MCP server configured with credentials

​
Response Fields

​
string
required
Success message
​
string
required
UUID of the MCP server that was authenticated
​
string
required
OAuth provider name (e.g., "google", "github", "slack")
​
string
required
ISO 8601 timestamp of when authentication completed

​
Status Codes