Skip to main content
POST
Connect an MCP server

Authorizations

Authorization
string
header
required

An API key from your Devic console, sent as Authorization: Bearer <key>. An embedded front end sends a tenant-session token instead, so no API key reaches the browser, and an OAuth integration sends its access token. Missing, invalid or expired credentials get a 401. See Authentication.

Headers

origin
string
required

Query Parameters

assistantId
string
required
agentId
string
required

Body

application/json
templateId
string

Id of an MCP server the developer offers pre-filled. Its url is used; any url in this body is ignored.

url
string

https url of a server the end user brings. Only when the assistant allows custom servers, and only without templateId.

name
string

Display name. Defaults to the template’s.

auth
object
returnTo
string

Absolute URL of the page starting the flow. Must match this request’s Origin or one of the assistant’s allowed widget sources. The popup is returned there once the authorization completes.

tenantId
string

Tenant, when not using a signed session.

subtenantId
string

End user inside the tenant. Omit to connect a server the whole tenant shares.

Response

Registered