MCP servers
Connect any tool that speaks the Model Context Protocol over HTTP, choose who can use its tools, and fix common connection errors.
On this page
Any tool with an MCP endpoint works with Duun, even if it isn’t in the catalog. Add a Model Context Protocol server and its tools show up for agents in the scope you choose. Use it for internal services, tools Duun doesn’t list yet, or a vendor’s official MCP server when you prefer it to the built-in connection.
Add a custom MCP server
- Open Settings → Integrations & MCP and select Add MCP server.
- Name it so agents and teammates recognise it, for example “Internal feature flags”.
- Paste the server URL. Use a full
https://URL, for examplehttps://mcp.example.com/mcp. - If the server needs authentication, add a token. It is sent as
Authorization: Bearer …. - Select Test connection. Duun lists the tools the server offers.
- Choose Who can use it and whether write tools are allowed, then select Add MCP server.
The toast confirms the server and how many tools it exposed, for example “Added MCP server Internal feature flags · 6 tools”.
Transport
Duun connects with Streamable HTTP, the Model Context Protocol’s HTTP transport. Servers must be reachable from the internet over HTTPS. Local stdio servers aren’t supported directly; run them behind an HTTP bridge, or on an SSH computer that agents use, and expose them there.
Authentication
| Server expects | What to enter |
|---|---|
| No auth | Leave the token empty |
| A static bearer token or API key | Paste it in the token field |
| A different header | Put the server behind a proxy that maps the bearer token to that header |
Tokens are stored as workspace secrets and appear in Settings → API keys & secrets, where you can rotate them. A rotated token is used from the next tool call.
Tool scopes
An MCP server’s tools follow the same rules as any integration:
- Scope decides which runs see the server: Just me, My team, Project or Whole workspace. See Connecting integrations.
- Read and write: tools are listed with what they do. Tools that change things count as writes and follow Action approvals, so with Ask for writes an agent’s call to
create_flagwaits for approval. - Agent tools: an agent with the relevant tool switched off can’t call the server’s tools that need it.
The server row lists every tool and when it was last synced, for example “synced 3m ago”. Duun refreshes the tool list periodically and when you select Test connection. Tools added on the server appear after the next sync.
Connector presets from Explore
For popular services, Explore has connector presets: MCP servers and integrations with their scopes and setup steps filled in, such as a Sentry MCP preset or a Linear triage preset. Choose Browse connector presets in Settings, or open Explore and filter by connectors. Selecting Connect on a preset walks you through the same steps with the URL and recommended scope prefilled.
See Install an item for how installs work.
Use MCP tools in workflows
Agents pick MCP tools on their own when a task needs them. To be explicit, name the tool or server in a step’s instructions:
Before planning, call the "Internal feature flags" server's list_flags tool
and include every flag that mentions {{trigger.issue.title}} in the plan.The run transcript shows each tool call with its arguments and the server’s response, so you can check what the agent saw.
Troubleshooting
| Message | What it means | Fix |
|---|---|---|
| Couldn’t reach the server (HTTP 401). Check the URL and token. | The server rejected the token | Paste a fresh token; check it has the scopes the server requires |
| Couldn’t reach the server (HTTP 404) | Wrong path | Many servers serve MCP at /mcp; check the provider’s docs |
| Use a full https:// URL | The URL is missing a scheme or uses http:// | Add https://; Duun doesn’t connect over plain HTTP |
| Test connection times out | The server is private or slow to start | Make it reachable from the internet, or warm it up and try again |
| Tools missing for an agent | Scope or tool permissions exclude it | Check the server’s scope and the agent’s tools |
If the server works with other MCP clients but not Duun, contact support with the time of the test and the Duun-Request-Id from the error details. See Contact support.
Remove a server
Choose Disconnect from the server’s menu. Agents lose access right away. Running jobs fail on their next call to it.
Related
- Connecting integrations
- Integration catalog
- Integration disconnected in the help center