External MCP servers

Connect your agent to external Model Context Protocol servers to give it access to tools beyond the built-in set. Once configured, the agent can call any tool exposed by your MCP servers during conversations.

When to use this

Use external MCP servers when you want the agent to:

• Query an internal API or database the agent doesn't already know about
• Take action in third-party systems (project management, CRM, ticketing)
• Use specialized tools your team has built and exposed via MCP

Add a server

1. Open Agent > MCP Servers in the dashboard.
2. Click Add MCP Server.
3. Fill in the connection details:

Field	Description
Name	Lowercase identifier (a-z, 0-9, -, _). The agent uses this to reference the server.
URL	The full HTTPS endpoint of the MCP server.
Transport	streamable-http (recommended) or sse for legacy servers.
Authentication	None, Bearer token, or Custom header.

For authenticated servers, paste the token or header value. Credentials are encrypted at rest and never returned by the API.

4. Click Add Server.

Discover tools

After adding a server, click Discover in its row. The agent connects to the server, fetches its tool list, and caches it. The Tools column shows the count once discovery succeeds.

You should re-run discovery when:

• The server's tool list changes (new tools added or removed)
• You changed the server's URL or auth credentials

Use tools in conversation

Once a server is enabled and tools are discovered, the agent can call them automatically. You don't need to reference the server explicitly — the agent picks the right tool based on what you ask:

• "Look up the open issues in our tracker assigned to me"
• "Create a new ticket for the login bug we just discussed"
• "Pull the latest sales numbers from the analytics service"

If you want to be explicit, you can tell the agent which server to use:

• "Use the github-mcp server to find recent pull requests"

Manage servers

Each server row supports:

• Discover — refresh the cached tool list
• Disable / Enable — temporarily turn the server off without deleting it. Disabled servers are hidden from the agent.
• Delete — permanently remove the server configuration

Disabling is useful when an upstream server is down or under maintenance — the agent will fall back to its other tools instead of failing on calls.

Security notes

• Only deployer and admin roles can add, edit, or delete MCP servers. Viewers have read-only access.
• Authentication credentials are encrypted before storage.
• Each MCP call is logged in conversation history with the tool name and result.
• The agent will not call a disabled server's tools, even if it remembers them from a previous discovery.

Troubleshooting

Discover fails with a connection error The MCP server URL is unreachable, or the server isn't speaking the selected transport. Confirm the URL in a browser or with curl, then check whether it expects streamable-http or sse.

Discover succeeds but the agent never calls the tools The agent picks tools based on tool descriptions. If your MCP server exposes tools without descriptions, the agent has no signal for when to call them. Update the server's tool definitions to include clear descriptions.

Tool calls return authentication errors Re-check the auth type and credentials in Agent > MCP Servers. Updating the auth config invalidates the cached tool list — re-run Discover afterward.