Integrations

Connect a remote MCP server as a custom integration

Re-probes the server: only tools the server really announces are stored; the body only chooses which are enabled and their read/write scope. visibility follows the usual rule ('company' = admins only, 'personal' = any member). Several connections may target the same server (one token each). Agents see enabled tools as <slug>.<tool> through the usual grants.

post/integrations/mcp/connections

Request

  • Base URL: https://api.atako.ai
  • URL: https://api.atako.ai/integrations/mcp/connections
  • Auth: HTTP bearer

Request body

displayNamestring
visibility'company' | 'personal'
urlstring uri required

Response

idstring uuid required
companyIdstring uuid nullable
providerKeystring required
displayNamestring required
authType'api_key' | 'oauth2' | 'mcp' | 'internal' required
visibility'company' | 'personal'

'company' = shared with the whole company, managed by its admins; 'personal' = visible to, managed and grantable (to their own agents) by its creator only. Another member's personal connections are never returned.

isMineboolean

Created by the caller.

status'active' | 'error' | 'revoked' required
externalLabelstring nullable
configobject nullable
scopesstring[]
lastUsedAtstring date-time nullable
createdBystring uuid
createdAtstring date-time required

Changes

No recorded changes to this operation across all 2 revisions of this API.