https://api.duvo.ai/v2/mcp. Connect to it from any MCP-compatible host — Claude, Cursor, ChatGPT connectors, your own client — and every Duvo Public API endpoint becomes a tool the host can call.
Use this to:
- Drive Duvo Agents from an AI assistant chat (“Start the invoice processor on yesterday’s batch and tell me when it’s done.”)
- Inspect Runs, Cases, and Files conversationally
- Build hybrid workflows where one assistant orchestrates Duvo Agents alongside other tools
What you can do
Every endpoint registered in the Public API is auto-exposed as an MCP tool. That includes:- Agents — list, get, create, update
- Runs — start, get status, send messages, respond to human-in-the-loop requests, stop
- Connections — list and inspect your authorized accounts
- Files — list, read, write, rename, delete
- Cases and Queues — inspect, delegate, label
- Clarity — create a process, invite people to interviews, see who has done theirs, and read the process summaries
- Skills, Plugins, Sandboxes — list and reference
Server URL
POST /v2/mcp). Most modern MCP hosts support this transport out of the box.
The earlier
https://api.duvo.ai/v1/mcp endpoint still works and serves the
same tools as /v2/mcp, so existing setups keep running unchanged — including
after the /v1 API sunset. New connections should use /v2/mcp.Authentication
The Duvo MCP server accepts two credential types:Option 1 — OAuth (recommended for personal use)
Recommended for hosts that prompt you to sign in (Claude, Cursor, ChatGPT connectors). The host runs a one-time browser-based sign-in to Duvo, then handles token refresh and revocation for you. No API key to copy or rotate. The exact steps depend on the host. In general:Add the server URL
Add
https://api.duvo.ai/v2/mcp as the MCP server URL in your host’s settings. In Claude, skip this step: connect Duvo from the connector directory instead.Trigger the OAuth challenge
The host detects the OAuth challenge and opens a browser tab to Duvo’s sign-in page.
Sign in and approve
Sign in and approve the connection.
Tokens stored automatically
The host stores the OAuth tokens and uses them automatically on every tool call.
https://api.duvo.ai/.well-known/oauth-protected-resource/v2/mcp (RFC 9728). Compliant MCP hosts use this to discover the authorization server and register themselves via Dynamic Client Registration automatically.
Option 2 — API key (recommended for scripts and service accounts)
Use API keys when the host doesn’t support OAuth, or for non-interactive use (CI, service accounts).Generate an API key
Generate a key in the Duvo dashboard at Your Profile → API keys, scoped to a single team or to all teams you can access. Users with the Manager role or above can also create keys that work only in one team at Team Settings → API keys.
Send the key as a bearer token
Configure the MCP host to send the key as a bearer token in the
Authorization header:Call tools
The host can then call Duvo MCP tools without any further sign-in.
Setup by host
In Claude, connect Duvo from the connector directory. Every other compliant host uses the same Duvo URL. Configuration syntax differs slightly between products, so check your host’s MCP setup guide for the exact field names. Common patterns:- Claude
- Claude Code
- Cursor
- ChatGPT (Custom Connector)
- Custom MCP host or script
Duvo is an official connector in Claude’s connector directory (see the Duvo listing), so there’s no URL to paste. The steps are the same on claude.ai and in the Claude desktop app.Need a manual setup instead? You can still add a custom connector with the URL
Open Connectors
In Claude, open Customize → Connectors.
Open the directory
Select the Discover tab.
Find Duvo
Search for Duvo.
Connect
Click Connect.
Sign in to Duvo
Sign in with your Duvo account in the browser tab that opens. Claude then uses the connection whenever it calls a Duvo tool.
On Team and Enterprise plans, an Owner or Primary Owner must first enable
the Duvo connector for your organization under
Organization settings → Connectors. Each person then connects and
signs in to Duvo individually.
https://api.duvo.ai/v2/mcp.Tool ergonomics
Tools follow the underlying Public API:- Tool names map to OpenAPI
operationIds (for example,listAgents,startRun,getConnection). - Tool descriptions come from each endpoint’s OpenAPI description.
- Input schemas are flat — path parameters, query parameters, and request body are merged into a single object so calls read naturally (
startRun({ agent_id: "...", input: "..." })rather than wrapping each section). - Responses match the corresponding API response. Use the Public API Reference for the exact shapes.
- Every tool carries MCP annotations (
readOnlyHint,destructiveHint,idempotentHint,openWorldHint), so hosts can tell a read from a write and know which tools reach outside Duvo — for examplestartRun,probeMcpServer, or the OAuth start tools. - Not-found errors name the id parameter that failed and echo the value you sent (for example
case_queue_id), so a call that takes several ids tells you which one to check.
Built-in skills
The server also ships Duvo’s Agent Skills as MCP resources, so your host has the same guidance without installing anything. Each skill is a markdown file underduvo://skills/:
The server’s instructions tell the host when to read each skill, and reference files sit next to each
SKILL.md under references/. Hosts that surface MCP resources (Claude Desktop, Claude Code, Cursor) list them automatically.
The skills are the same content as the public
duvoai/skills repository,
which you can still install locally to use with the Duvo CLI.Limits and behavior
- All Public API rate limits apply to MCP tool calls.
- Every tool call respects the permissions of the authenticating user, just like a direct API call.
- Long-running Runs are not streamed over MCP today — start the Run via the tool, then poll
getRunorlistRunMessagesto monitor progress.
Troubleshooting
Privacy and terms
- Privacy Policy — how Duvo handles data accessed through the MCP server.
- Terms of Use — the terms that apply to Duvo API and MCP usage.
Related
Available MCP Tools
The full catalog of tools this server exposes.
Connect a custom MCP to Duvo
The other direction: bring your own MCP server into Duvo.
Public API Reference
The API the Duvo MCP server wraps.
Duvo CLI
Terminal-first wrapper over the same API.