Skip to main content
The Model Context Protocol (MCP) is an open standard that lets AI assistants and platforms exchange tools, context, and data. Duvo speaks MCP in two directions, and this section of the docs is organized around them. If you’re new to MCP, the official MCP documentation is a good starting point.

​
The two directions

​
1. Drive Duvo from an MCP host — the Duvo MCP server

Duvo runs a hosted MCP server. Connect a host like Claude Desktop, Claude Code, Cursor, or ChatGPT to it, and every Duvo Public API endpoint becomes a tool that host can call — start Jobs, inspect Cases, manage Files, all from an assistant chat. This is the main way teams use MCP with Duvo, and it’s the counterpart to the Duvo CLI: another way to operate Duvo from outside the dashboard. Start here: The Duvo MCP server.

​
2. Bring your own MCP into Duvo — Custom MCP Connections

Run an MCP server of your own — for an internal system, a legacy platform, or a custom API — and add it to Duvo as a Connection. Your Assignments then call its tools alongside built-in Connections like Gmail or Snowflake. Start here: Connect a custom MCP to Duvo, and Build an MCP server for Duvo if you’re implementing the server yourself.

​
Which direction do you need?

You want to…Go to
Drive Duvo from Claude Desktop, Claude Code, Cursor, ChatGPT connectors, or another hostThe Duvo MCP server
See exactly which Duvo actions are available as MCP toolsAvailable MCP Tools
Call Duvo Assignments as tools from your own AI agent or copilotEmbedding Duvo as a tool
Let your Duvo Assignments call tools from a custom internal systemConnect a custom MCP to Duvo
Build an MCP server from scratch to expose your own toolsBuild an MCP server for Duvo

​
The two directions at a glance

Duvo as MCP serverCustom MCP Connections
Who runs the serverDuvoYou
Endpointhttps://api.duvo.ai/v2/mcpA public HTTPS URL you provide
What tools it exposesEvery Duvo Public API endpointWhatever your MCP server implements
Who’s the client (host)Claude Desktop, Claude Code, Cursor, ChatGPT connectors, or any MCP-compatible appDuvo Assignments
AuthenticationOAuth or API keyNone, API key, custom headers, or OAuth (DCR-aware)
Setup timeMinutes — paste the URL into your MCP hostMinutes once your server is deployed and reachable

​
How MCP fits alongside the CLI and API

MCP is one of three ways to drive Duvo from outside the dashboard, all built on the same Public API:
  • The Duvo MCP server is a thin layer over the Public API — the same authentication, rate limits, and permissions apply. Best when you want to operate Duvo conversationally from an AI host.
  • The Duvo CLI wraps the same API for terminal-first and CI/CD workflows.
  • The Public API itself is the foundation both build on — use it directly when you’re writing your own integration.
Custom MCP Connections are different: they don’t drive Duvo, they extend what your Assignments can do. They appear in the dashboard alongside other Connections, and Assignments use them the same way they use Gmail or Slack.