Sign in
integrations

Connect a customer-supplied MCP server (static creds or OAuth)

Static-cred connections are born active; OAuth returns an authorize_url + state and the row starts pending_oauth until the /integrations/oauth/callback redirect lands. server_url (and any OAuth endpoint URLs) are SSRF-validated in the service layer.

post/v1/integrations/connections/custom-mcp

Request body

nicknamestring required
server_urlstring required
transportstring
auth_typestring
tokenstring nullable
api_keystring nullable
api_key_headerstring
headersobject
oauth_authorize_urlstring nullable
oauth_token_urlstring nullable
oauth_client_idstring nullable
oauth_client_secretstring nullable
oauth_scopesstring[]

Response

Successful Response

connection_idstring uuid required
statusstring required
vendorstring required
authorize_urlstring nullable
statestring nullable

Changes

Changed in 1 of the 3 revisions of this API.4

  • 5a5597ebb2d64See the full diff
    • ○

      added the optional property retry_after to the response with the 400 status

      response-optional-property-added

    • ○

      added the optional property retry_after to the response with the 401 status

      response-optional-property-added

    • ○

      added the optional property retryable to the response with the 400 status

      response-optional-property-added

    • ○

      added the optional property retryable to the response with the 401 status

      response-optional-property-added

    This revision also has 40 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog