Skip to main content
Connections in Duvo are your personal authorized accounts linked to integrations — for example, your Gmail or Slack account. The CLI lets you list and inspect Connections from the terminal, and discover which Connection types your team has enabled. For an overview of what Connections are and how to add new ones, see Connections Overview and How to Add a Connection.

​
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.
Each entry shows the Connection type’s 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 so Connections can be created against it:
--auth-method is required and must be one of url (no auth), apikey, headers, or oauth. For oauth, pair it with --oauth-client-id and --oauth-client-secret if your server isn’t DCR-capable.

​
Listing your Connections

duvo connections shows the Connections you’ve personally authorized.
The table includes the Connection ID, name, Connection type, provider, and creation date. Use the ID with duvo connections get or to pin a Connection to a Revision (see Advanced commands).

​
Inspecting a single Connection

The output includes the integration metadata and which credential fields are configured. Secret values (API keys, tokens, passwords) are never returned — the response only tells you which fields are set, not their values.

​
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.
Provide exactly one of --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:
See Advanced commands → Pinned Connections for the full reference.

​
Authorizing a Connection from the CLI

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.
For credential-based Connections (username/API key) rather than OAuth, see Secrets and Logins, or call the Public API directly.