Beyond the built-in connectors, you can bring your own tools by connecting a custom MCP (Model Context Protocol) server. Any HTTP or SSE MCP server — Jira, Notion, an internal API, or something you built — becomes a set of tools your agents can use.

​
Where to Manage Them

Custom MCP servers live in the Connectors modal, which you can open from several places: the sidebar, the connector-health card on Home, the tools menu in chat, and an agent’s tool chips. The Connectors modal has two tabs:
  • Apps — the built-in connector catalog
  • Custom MCP — your own MCP servers
Custom MCP tab in the Connectors modal

​
Adding a Server

On the Custom MCP tab, click Add custom MCP. You’ll be asked how you want to add it:
  • Direct configuration — fill in the details by hand (click Configure)
  • Import from JSON — paste an existing MCP server config and we’ll pre-fill the form (click Import)

​
Direct configuration

Direct add is a two-step wizard.
1

Details

Enter a Server Name (required) and optional Instructions for the agent — guidance on how and when the agent should use this server’s tools. Click Continue.
2

Configuration

Choose a Transport (Streamable HTTP or SSE), enter the Server URL (required), and add any Custom headers (optional) as name/value pairs — header values are masked.
3

Test the connection

Click Test connection. On success you’ll see a green check and the discovered tool count, for example “Connected — discovered 5 tools.” You must test before you can save.
4

Save

Once the test passes, save the server. It appears as a card on the Custom MCP tab.
A connection has to be tested successfully before it can be saved. Only HTTP and SSE servers are supported — stdio servers are not.

​
Managing Servers

Each server shows as a card with a health badge — Healthy (green), Connection error (red), or Not tested (blue) — and its tool count. The ⋯ menu offers Edit, Test connection, and Delete.
Deleting a server also removes any agents’ access to its tools. If agents are using it, you’ll see a warning before you confirm.

​
Sharing a Server with an Agent

Custom MCP servers are private to you in Connectors. To let others use one, add it as a tool on an agent through the agent’s tools picker, where it appears as a tool chip. Recipients of that agent can use the server’s tools through the agent only — it won’t appear in their own Connectors. The Workflow Builder also offers an mcp node type for use in workflows.

Integrations Overview

Browse all available connectors.

Setting Up a Connector

Connect a built-in third-party service.

Agents Overview

Learn what agents are and how they work.

Workflow Builder

Use an mcp node inside a workflow.