MCP OAuth Callback
MCP OAuth Callback
OAuth callback endpoint for completing MCP server OAuth flows.
POST
MCP OAuth Callback
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 viaAuthorization: Bearer <token> header.
MCP server UUID
OAuth authorization code from provider
OAuth state parameter (for CSRF protection)
Example Request
Example Response
OAuth Flow
This endpoint is step 4 in the OAuth flow:- User calls
/mcp/servers/{id}/oauth/authorize - OAuth provider shows authorization page
- User grants permissions
- Provider redirects here with authorization code ← This endpoint
- Backend exchanges code for access token
- MCP server configured with credentials
Response Fields
Success message
UUID of the MCP server that was authenticated
OAuth provider name (e.g.,
"google", "github", "slack")ISO 8601 timestamp of when authentication completed
Status Codes
| Code | Description |
|---|---|
200 | OAuth authentication successful |
400 | Invalid or expired authorization code |
401 | Unauthorized - invalid or missing authentication |
404 | MCP server not found |

