Available Connection types
duvo integrations is the catalog of services your team has enabled in Duvo. Use it to find Connection-type IDs that you can pass to other commands.
id, name, type, provider, and auth_method (none, OAuth, API key, custom headers, etc.).
Custom integrations
If your team uses a custom MCP server, register it as a custom integration first. Connections to a custom MCP server are created against a custom integration; one created from a URL alone is refused. Registering a custom integration needs the Manager role or above:--auth-method is required and must be one of url (no auth), apikey, headers, or oauth. For oauth, pass --oauth-client-id (and --oauth-client-secret, unless it is a public PKCE-only client) if your server isn’t DCR-capable.
For a server that doesn’t use OAuth, connect through the custom integration with duvo connections create. Its --auth-method must match the custom integration’s; this example is for one registered with --auth-method headers. For oauth, see Authorizing a Connection from the CLI.
Listing your Connections
duvo connections shows the Connections you’ve personally authorized.
duvo connections get or to pin a Connection to a Revision (see Advanced commands).
Inspecting a single Connection
Probing a connection’s tool catalog
duvo connections probe tests connectivity and lists the tools a connection exposes — a dry run before wiring a connection into an Agent.
--slug or --url. On success it prints the tool list; add --json for raw output. For connections whose tool listing isn’t available yet (for example, one that only exposes tools once connected), it prints a short notice and exits 0 — that’s expected, not a failure. A genuine probe failure (unreachable server, rejected credentials) exits non-zero.
Common workflows
Find the Connection ID for a specific account
When you have multiple Gmail Connections (different mailboxes, for example) and need to reference a specific one in a Revision:Pin a Connection to an Agent Revision
Once you have the Connection ID, pin it so the Agent always uses that account:Authorizing a Connection from the CLI
duvo oauth native start <provider-key> uses the native OAuth provider key,
not the integration type; find it in duvo integrations list --json as
oauth_provider_key. See the provider key table.
OAuth-based Connections require a browser consent step, so duvo oauth starts the flow and hands you the authorization URL to open. Once you approve in the browser, the Connection is created on your account.
These commands kick off interactive OAuth flows. For the full setup experience
— including which providers your team has enabled — the Connections
page in the dashboard remains the simplest
path.