Custom MCP

What is the Custom MCP Connection?

The Custom MCP connection lets you link Duvo to any system not covered by a built-in connection. You provide the URL of your own MCP-compatible server, and Duvo connects to it to give your assignments access to the tools that server exposes. This is a user-provided connection that requires a deployed MCP server and, optionally, API credentials.

What Can It Do?

The Custom MCP connection enables your assignments to:

• Access proprietary systems: Connect to internal tools, legacy platforms, or custom-built APIs not available as standard connections

• Call custom tools: Use any tools exposed by your MCP server directly within assignment workflows

• Authenticate securely: Support API key or OAuth-based authentication depending on your server's requirements

• Extend Duvo's capabilities: Add domain-specific functionality tailored to your organization's needs

Why This Matters

Every organization has unique systems and data sources. Standard connections cover common platforms, but custom workflows often require integrations with internal databases, proprietary software, or industry-specific tools. The Custom MCP connection removes that constraint—if you can build and deploy an MCP server for a system, Duvo can work with it.

When to Use It

Use the Custom MCP connection when your assignment needs to:

• Integrate with internal tools: Connect to systems built in-house that have no off-the-shelf connection

• Access industry-specific platforms: Work with specialized software used in your sector

• Prototype new integrations: Test a custom integration before it becomes a standard connection

• Extend existing workflows: Add capabilities beyond what built-in connections provide

How It Works

You deploy an MCP server that implements your tools and exposes them over streamable HTTP. Once deployed, you add it as a Custom MCP connection in Duvo by providing:

1. Server URL: The public HTTPS URL of your deployed MCP server

2. API credentials (if required): API key or OAuth client ID and secret, depending on your server's authentication method

Requirements for your MCP server:

• Must be accessible over the internet (cloud-hosted; localhost is not supported)

• Must support streamable HTTP transport (STDIO and HTTP/SSE are not supported)

If your server uses OAuth:

When you select OAuth as the authorization method, Duvo automatically checks whether your MCP server supports dynamic client registration (DCR). If it does, no Client ID or Secret is needed — the connection is handled automatically.

If the server does not support DCR, or if you prefer to use your own pre-registered OAuth app, expand the Advanced settings section to provide your Client ID and Client Secret. This section also contains a step-by-step guide with a redirect URI (https://platform.duvo.ai/v1/oauth/mcp/callback) you need to register in your OAuth provider.

For guidance on building an MCP server, see Building Custom Connections.

Key Benefits

Unlimited integration scope: Connect to any system you can build an MCP server for, without waiting for a built-in connection to exist.

Full control: You own and manage the server, so you control what tools are available and what data is exposed.

Consistent workflow: Custom tools work the same way as built-in connections—your assignments can use them without special handling.

Secure by design: Credentials stay within Duvo's connection setup and are not exposed in assignment instructions.

Works Well With

Custom MCP + Browser: Use a custom MCP server to pull data from a proprietary system, then use the Browser connection to enter that data into a web-based downstream tool.

Custom MCP + Gmail or Outlook: Retrieve records from an internal system via custom MCP and send automated email summaries using a standard email connection.

Custom MCP + Snowflake or BigQuery: Fetch data from a proprietary operational system through custom MCP and combine it with warehouse queries for unified reporting.