Create enterprise SSO verification

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL


        
          
            https://openapi.logto.io/mcp

Standard setup for AI tools providing an mcp.json file

{
  "Logto API references MCP server": {
    "url": "https://openapi.logto.io/mcp"
  }
}

POST /api/experience/verification/sso/{connectorId}/authorization-uri

Create a new EnterpriseSSO verification record and return the provider's authorization URI for the given connector.

Path parameters

connectorId string Required

The unique identifier of the connector.

application/json

Body Required

state string Required

The state parameter to pass to the SSO connector.
redirectUri string Required

The URI to redirect the user after the SSO authorization is completed.

Responses

200 application/json

The SSO authorization URI has been successfully generated.
Hide response attributes Show response attributes object
- authorizationUri string Required
  
  The SSO authorization URI.
- verificationId string Required
  
  The unique verification ID of the newly created EnterpriseSSO verification record. The verificationId is required when verifying the SSO authorization response.
400

Bad Request
403

In a step-up authentication, only a connector listed in subjectProofConnectors of the interaction is accepted, as proof of the pinned subject (session.step_up.forbidden_route).
404

The SSO connector is not found.
500

Connector error. Failed to generate the SSO authorization URI.

POST /api/experience/verification/sso/{connectorId}/authorization-uri

curl \
 --request POST 'https://[tenant_id].logto.app/api/experience/verification/sso/{connectorId}/authorization-uri' \
 --header "Content-Type: application/json" \
 --data '{
  "state": "string",
  "redirectUri": "string"
}'

Request examples

{
  "state": "string",
  "redirectUri": "string"
}

Response examples (200)

{
  "authorizationUri": "string",
  "verificationId": "string"
}