Connect to the Duvo MCP server

Connecting an MCP host to the Duvo MCP server is the main way teams use MCP with Duvo — it’s the conversational counterpart to the Duvo CLI. Duvo exposes a hosted MCP server at https://api.duvo.ai/v2/mcp. Connect to it from any MCP-compatible host — Claude Desktop, 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
Skills, Plugins, Sandboxes — list and reference

See the full list of available tools on the Available MCP Tools page. When Duvo ships a new Public API endpoint, it automatically becomes an MCP tool on the next deploy. There’s no separate maintenance step.

Server URL

https://api.duvo.ai/v2/mcp

The server uses MCP’s Streamable HTTP transport (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 Desktop, 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.

Trigger the OAuth challenge

The host detects the OAuth challenge and opens a browser tab to Duvo’s sign-in page.

Tokens stored automatically

The host stores the OAuth tokens and uses them automatically on every tool call.

Duvo’s MCP server publishes its OAuth metadata at 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 a team’s keys 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:

Authorization: Bearer <your-api-key>

Call tools

The host can then call Duvo MCP tools without any further sign-in.

API keys are scoped to a single team or to all teams the owner can access, and inherit the permissions of the user who generated them.

Setup by host

The MCP standard means the same Duvo URL works in every compliant host. Configuration syntax differs slightly between products, so check your host’s MCP setup guide for the exact field names. Common patterns:

Claude Desktop
Claude Code
Cursor
ChatGPT (Custom Connector)
Custom MCP host or script

Edit your Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "duvo": {
      "url": "https://api.duvo.ai/v2/mcp"
    }
  }
}

Restart Claude Desktop. When you mention Duvo or use a tool from the connector, Claude Desktop opens a browser tab for OAuth sign-in.

Add the Duvo server from your terminal with the claude mcp add command:

claude mcp add --transport http duvo https://api.duvo.ai/v2/mcp

The first time you call a Duvo tool, Claude Code runs the browser-based OAuth sign-in. To use an API key instead (for CI or service accounts), pass it as a bearer header:

claude mcp add --transport http duvo https://api.duvo.ai/v2/mcp \
  --header "Authorization: Bearer <your-api-key>"

In Cursor settings, open the MCP servers section, add a new server with the URL https://api.duvo.ai/v2/mcp, and let Cursor run the OAuth flow.

Add a Custom Connector pointing to https://api.duvo.ai/v2/mcp. ChatGPT handles Dynamic Client Registration and the OAuth flow automatically.

Any MCP-compatible client library (TypeScript, Python, etc.) can connect — point it at https://api.duvo.ai/v2/mcp, supply either an OAuth token or an API key, and call tools/list to discover what’s available.

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.

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 getRun or listRunMessages to monitor progress.

Troubleshooting

401 Unauthorized — Your token is missing, expired, or for a different audience. Re-run OAuth, or regenerate the API key in the dashboard.

403 Forbidden — Your account doesn’t have permission to call this endpoint. Check your team role and Connection permissions.

OAuth doesn’t open a browser — The host may not support Dynamic Client Registration. Fall back to API key authentication, or check the host’s docs for OAuth setup steps.

Privacy and terms

For platform-wide details (SOC 2 certification, encryption, Anthropic Zero Data Retention, sub-processors), see Security & Privacy.

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.

Overview

The Duvo MCP server

Bring your own MCP

Connect to the Duvo MCP server

What you can do

Server URL

Authentication

Option 1 — OAuth (recommended for personal use)

Option 2 — API key (recommended for scripts and service accounts)

Setup by host

Tool ergonomics

Limits and behavior

Troubleshooting

Privacy and terms

Available MCP Tools

Connect a custom MCP to Duvo

Public API Reference

Duvo CLI

​What you can do

​Server URL

​Authentication

​Option 1 — OAuth (recommended for personal use)

​Option 2 — API key (recommended for scripts and service accounts)

​Setup by host

​Tool ergonomics

​Limits and behavior

​Troubleshooting

​Privacy and terms

​Related

Available MCP Tools

Connect a custom MCP to Duvo

Public API Reference

Duvo CLI

What you can do

Server URL

Authentication

Option 1 — OAuth (recommended for personal use)

Option 2 — API key (recommended for scripts and service accounts)

Setup by host

Tool ergonomics

Limits and behavior

Troubleshooting

Privacy and terms

Related