Authorize MCP Server

Start the OAuth authorization flow for an MCP server that requires it. Answers a redirect, so open it in a browser rather than following it with an HTTP client: the flow depends on the `oauth_state` cookie set alongside the redirect, and finishes at the callback below. Nothing is stored against a server here — the callback hands back an `auth_session_id` to pass to registration.

Authentication

AuthorizationBearer

API key or access token, sent as Authorization: Bearer <token>. The simplest option: create an API key in your dashboard under Settings, then paste it here.

OR
AuthorizationBearer

API key or access token, sent as Authorization: Bearer <token>. The simplest option: create an API key in your dashboard under Settings, then paste it here.

Path parameters

org_idstringRequiredformat: "uuid"
The unique identifier of the organization.
project_idstringRequiredformat: "uuid"
The unique identifier of the project.

Query parameters

server_urlstringRequired

The remote MCP server’s URL, as an http(s) URL.

redirect_tostring or nullOptional

Console URL to return the browser to once the flow finishes. Must be under the configured console origin. When supplied, a failure to start the flow redirects here with an error query parameter instead of answering 400.

Errors

400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
422
Unprocessable Entity Error
500
Internal Server Error