API

Connectors

Add, test, rotate and remove connectors.

See Connectors.

Every route below, with its parameters, request and response, errors and samples, is in the API reference.

RouteWhat it does
GET /v1/orgs/:orgId/connectorsLists connectors. Credentials are never returned. Also limit, the plan's maxConnectors.
GET /v1/orgs/:orgId/connectors/:connectorIdA connector with its cached tools and the names they have on the MCP server.
POST /v1/orgs/:orgId/connectorsRegisters a remote MCP server.
POST /v1/orgs/:orgId/connectors/:connectorId/testConnects to the server and caches its tool list. A failed check keeps the last good list and records the error.
PATCH /v1/orgs/:orgId/connectors/:connectorIdRenames, enables or disables a connector, or replaces its credential.
DELETE /v1/orgs/:orgId/connectors/:connectorIdDeletes a connector.
POST /v1/orgs/:orgId/connectors/:connectorId/oauth/startOAuth connectors: finds the server's sign-in (and registers a client when the server allows it), stores a one-time state with a PKCE verifier and returns the authorization URL to send the user to.
POST /v1/orgs/:orgId/connectors/oauth/callbackCompletes a connector sign-in: consumes the state (one use; same user and org), exchanges the code, stores the tokens encrypted and checks the connector's tools with them.
DELETE /v1/orgs/:orgId/connectors/:connectorId/oauth/sessionSigns out: the caller's own sign-in to a per-person connector, or the shared sign-in (connectors:write).