Skip to main content
POST
Connect an MCP server

Authorizations

Authorization
string
header
required

An organization-scoped API key, minted in control under Settings → API keys. Every failure to authenticate answers one identical 401: "Provide a valid organization-scoped API key or an active session." Each operation names the one scope it is filed under, <resource>:<read|write>, where the resource is the first path segment after /api/v1/; a key minted today carries all 22 of them. Scopes are RECORDED — on the key and on every audit row — and are not yet enforced: no request is refused for want of one.

Headers

Idempotency-Key
string

Any unique string.

Body

application/json
serverUrl
string
required

The MCP server's URL. Must be publicly reachable.

key
string
required

The key the registration will be stored under.

scope
enum<string>

Org-wide or for one Client. There is no worker scope for an MCP registration.

Available options:
org,
client
clientId
string

Required when scope is client.

Response

Success — the server needs no credential, so the connection is already complete.

data
object
required