Skip to main content
GET
Begin MCP OAuth authorization
No signed-in session is required. Endpoint-specific tokens, setup secrets or challenges may still be required. Validates the client, exact redirect URI, MCP resource and S256 PKCE challenge, then redirects to Posted’s human consent flow. The human chooses the access level. Request conventions · API keys · MCP connections

Query Parameters

response_type
string
required

string

Allowed value: "code"
client_id
string
required

string

redirect_uri
string<uri>
required

uri

code_challenge
string
required

string

code_challenge_method
string
required

string

Allowed value: "S256"
resource
string<uri>
required

uri

state
string

string

scope
string

string

Response

Redirect to the authorization, consent or UI destination.