Start the OAuth authorization flow for an MCP server
GEThttps://platform.docana.com/api/v1/mcp-servers/oauth/authorize/
Discovers the MCP authorization server, registers a client when needed, builds a PKCE authorization request, and answers the provider authorization URL as JSON. The endpoint itself never issues a 302. After consent the provider redirects back to /api/oauth/mcp/callback, which stores the tokens read by GET /api/v1/mcp-servers/{mcpServerId}/connection/.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 500
The provider authorization URL
MCP server is not configured for OAuth or its URL is invalid
The API key or session is missing, expired, or malformed.
The caller is authenticated but not allowed to perform this operation.
MCP server not found
State-signing misconfiguration or provider error