Skip to main content
If an app you use isn’t in Daoco’s integration list but has a remote MCP server, you can add it yourself with the server’s URL. Daoco can then use that server’s tools from chat, recurring tasks, and your AI apps. A brand can add up to 15 custom servers. Each one is its own connection.

Before you start

  • Find the app’s remote MCP server URL in its docs. It usually ends in /mcp or /sse, for example https://mcp.example.com/mcp. Servers you run on your own computer, which you start with a command, can’t be added.
  • The address must be public https on the standard port.
  • Some servers need an API key or access token instead of a sign-in. If so, create one in the app first. Daoco sends it as a bearer token (Authorization: Bearer <token>), which is what most MCP servers expect. A server that wants the key in another header can’t be added yet.

Add a server

1

Open the custom server form

In Daoco, open Connections -> Integrations -> Add integration, scroll to Don’t see your app?, and choose Add a custom MCP server.
2

Enter the URL and a name

Paste the server URL. You can give it a name, like Acme CRM. Daoco uses the name when it talks about the server. If you leave it blank, Daoco uses the server’s address. If you already have an API key or access token for the server, choose Use an API key or token and paste it.
3

Connect

Choose Connect. Daoco checks the server, then:
  • connects it straight away if it needs no sign-in;
  • opens the app’s sign-in window if the server offers one;
  • asks for an API key or access token if it needs something Daoco can’t sign in to for you. Paste the token and choose Connect again.
When the server is connected, the form closes and the server appears in your list of integrations.
Daoco lists the server’s tools before it saves the connection. If it can’t list them, the server isn’t added and the form says why. Tools whose names use characters other than letters, numbers, _, ., and -, or whose inputs are too large or unusual for Daoco to describe, are left out. To reconnect a server, choose Reconnect on its card, or on the reconnect card in chat when a request stopped because the server’s sign-in expired. Daoco keeps the last working sign-in until the new one works, so a mistyped token doesn’t take the server offline. If you start connecting a server again, or remove it, before an earlier sign-in window finishes, that earlier sign-in isn’t saved. To remove a server, disconnect it from its card. Some MCP links carry a private key in the address itself. Daoco keeps the full address on its servers and never shows it again: the Connections page shows only the server’s domain, and error messages leave the address out. The address itself is stored as you entered it; API keys, tokens, and sign-in secrets are encrypted. When the server signs you in, Daoco doesn’t put the address in the sign-in window’s link: it names only the resource the server advertises for itself, and only if that repeats no part of the address’s path or query other than generic words like mcp. If the server’s sign-in link would still include part of the address, Daoco doesn’t open it and asks for an API key or access token instead. Error messages also leave out the key or tokens Daoco sends the server.

What Daoco asks before it acts

Daoco hasn’t reviewed what a custom server’s tools do, so:
  • Tools the server marks as read-only run without asking.
  • Every other call asks you first, every time. Approving one call never approves the next. Autonomy presets, recurring tasks, assistant grants, the connection’s Never ask setting, and turning approvals off for a thread can’t answer for you.
A custom server acts with your account in that app. Only add servers from apps you trust, and read each approval card before you approve it.

When a server won’t connect