Skip to main content
To connect an MCP server to Duvo, add it as a Custom MCP Connection. Your Duvo Assignments can then call its tools from an MCP server you host — use this when a built-in Connection doesn’t cover the system you need (internal tools, legacy platforms, custom-built APIs) and you’d rather expose those tools via MCP than build a one-off integration. To Duvo, a Custom MCP Connection looks like any other Connection. Your Assignment’s Setup picks tools from your MCP server alongside tools from Gmail, Slack, or Snowflake. If you haven’t built the server yet, see Build an MCP server for Duvo first. If instead you want to drive Duvo from an MCP host, see The Duvo MCP server.

​
When to use a Custom MCP Connection

  • You have a proprietary internal system (CRM, warehouse API, internal tool) that isn’t a built-in Duvo Connection.
  • You’ve already built or can build an MCP server for that system.
  • You want consistent setup across teammates — add the Connection once, every teammate can connect with their own credentials.
If you want to drive Duvo from an MCP host instead, see The Duvo MCP server.

​
What you need to bring

  • A deployed MCP server accessible over the internet via a public HTTPS URL. Localhost is not supported.
  • Streamable HTTP transport. Servers that only support STDIO or HTTP/SSE cannot connect.
  • Your authentication method — Custom MCP supports no-auth, API key, custom HTTP headers, and OAuth (with automatic Dynamic Client Registration where available).

​
Setup at a glance

Full step-by-step instructions live on the Custom MCP Connection page: Custom MCP. The short version:
  1. Open the Connections page in Duvo and click Add custom connection.
  2. Give the Connection a recognizable name (for example, “Internal CRM”).
  3. Pick an authorization method (None, API key, custom headers, or OAuth).
  4. Enter your server’s public HTTPS URL.
  5. Click Create. Teammates then sign into the Connection individually with their own credentials.

​
OAuth support

If your MCP server uses OAuth, Duvo automatically detects whether it supports Dynamic Client Registration (DCR, RFC 7591):
  • DCR-capable servers — Duvo registers itself automatically. No Client ID or Secret required.
  • Servers without DCR — Provide your own Client ID and Client Secret in the Advanced settings when setting up the Connection. Duvo displays the redirect URI you need to register on your OAuth provider.
You can also force the manual path if you’d rather use a pre-registered OAuth app instead of auto-registration.