MCP servers

Already have an MCP server for your own systems? Connect it and the agent can use the tools you allow from it — for example looking up an order in your own order system.

Connect

1. In the console go to Settings → Integrations → MCP servers.
2. Enter the Server URL — a public https:// address using Streamable HTTP, usually ending in /mcp.
3. Give it a Name (for example Order system).
4. If the server needs a key, enter the Auth header (for example Authorization) and the Key or token. Leave the key empty if the server needs none.
5. We ask the server for its tools before saving.

Add more servers with Add server on the integration’s page — up to 10 per workspace. Only a fixed key in a header is supported; servers that require their own sign-in screen cannot be connected.

Choose the tools

Each server lists its tools. Allow the ones the agent may use, then Save tools.

• Read-only tools run without asking.
• Tools that change data first ask the customer, then wait for your approval in Conversations.
• You can mark a read-only tool as changing data to put it behind both approvals. The other way round is not possible.

When a tool changes on the server

The agent sees each tool exactly as it was when you allowed it. If the server changes a tool, it shows as Changed on the server and the agent cannot use it until you allow it again.

Good to know

• Use Test to check a server again. Its status shows Answering, Not answering or Key refused — update the key from the same card.
• Private-network addresses and addresses with a user name or password in them are not accepted.
• Removing a server deletes its key here. The key itself stays valid until you delete it where you created it.

Prefer a single HTTP endpoint instead? See Custom tools.