Skip to content

MCP Connections

MCP Connections let your AI agents use tools from external Model Context Protocol (MCP) servers, such as a vendor’s API exposed as MCP tools. You register the server once, review and approve (“pin”) the tools it offers, and then grant specific tools to specific agents.

Connections are managed under Administration > Integrations > MCP Connections. The list shows each Connection, its Server URL, and a Status chip (Connected, Pending Auth, Error, Disabled, Drift Review, or Not Connected).

  1. Click New MCP Connection

  2. Enter a Connection Name, the Server URL (https), and an optional Description

  3. Choose the Transport (Streamable HTTP, or SSE (legacy) for older servers)

  4. Choose Authentication: OAuth 2.1, Static Bearer Token, Custom Headers, or None. Tokens and header secrets are stored encrypted and never shown again

  5. Check I understand this external server will receive tool inputs from my agents and save

  6. For OAuth connections, click Connect to authorize with the external service

After saving, click Sync Tools to discover the server’s tools. Each tool shows whether it reads or writes, and its review state: Pinned (approved), New - review, or Changed - review when the server has altered a tool since you approved it. Click Pin to approve a tool’s current definition; agents can only be granted tools you have pinned, and a changed tool goes back to review rather than silently taking effect.

Use Test to verify the connection is healthy at any time.

Granting happens on the agent, not here: open the agent’s automated-action editor and choose the pinned tools it may use under its tools settings. An agent never sees tools you haven’t granted it.