Add your own MCP server
Bring your own tools by registering a custom MCP (Model Context Protocol) server — give it a name, a Streamable-HTTP URL and an optional token, and the agent auto-discovers its tools and calls them when a goal needs them. For pre-built SaaS actions (Slack, HubSpot, Salesforce and more), connect Composio instead.
Add a custom MCP server
Go to the Integrations page and find the Custom MCP servers card. Your server must speak MCP over Streamable-HTTP (JSON-RPC 2.0 over HTTP POST).
- 1Integrations → Custom MCP servers → “+ Add MCP server”.
- 2Name: a short identifier for the server (e.g. “my-crm”).
- 3Server URL: your Streamable-HTTP endpoint (e.g. https://your-mcp.example.com/mcp).
- 4Auth header: the header name to send your token in (defaults to “Authorization”).
- 5Token / PAT: optional — leave blank for public servers. It’s encrypted at rest and never returned to the browser.
- 6Save & discover tools — the client runs the MCP handshake and lists the server’s tools; the discovered count is shown.
How the agent uses your tools
Once discovered, your MCP tools load automatically when the orchestrator plans. If a tool is relevant to the goal, the planner calls it by name — no extra wiring. Tool results flow back into the plan like any built-in tool, and any tool that writes still passes through the approval gate.
- Protocol: MCP Streamable-HTTP (JSON-RPC 2.0 over POST).
- Stateful sessions: the client reuses the server’s session id across calls.
- Responses: both plain JSON and SSE data frames are supported.
- Security: tokens are encrypted at rest and scoped to your organization.
Composio — thousands of SaaS actions
If you don’t want to host a server, connect Composio from the Integrations page with your Composio API key. It exposes pre-built actions across 250+ SaaS apps (Slack, HubSpot, Salesforce, Notion and more) that the agent can call the same way as MCP tools — see the full Connect & use Composio guide.
Frequently asked questions
- What protocol does my server need to speak?
- MCP over Streamable-HTTP — JSON-RPC 2.0 over HTTP POST, with the standard initialize handshake and tools/list discovery. The client also handles SSE-framed responses and session ids.
- Is my token safe?
- Yes. The token is encrypted at rest, scoped to your organization, and never sent back to the browser.
- Composio vs custom MCP — which should I use?
- Use Composio for pre-built SaaS actions you don’t want to build. Use a custom MCP server to expose your own internal tools or data over an endpoint you host.