Authorize MCP OAuth
Start an OAuth-based connection with a remote MCP server using Dynamic Client Registration. Returns an authorization URL the user must open in a browser; once they grant consent, Duvo creates the matching connection and redirects the browser to the optional returnUrl.
Authorizations
API key authentication. Get your API key from the Duvo dashboard.
Path Parameters
Body
URL of the MCP server requiring OAuth.
Human-readable name to display for the connection.
1Optional ID of a custom integration this connection should be associated with.
Where to send the user's browser after consent completes. Accepts an absolute URL on a domain Duvo allows, or a path relative to the Duvo frontend (e.g. /integrations/slack).
Optional catalog integration type (e.g. netsuite, asana). When it names a known MCP OAuth catalog integration and mcp_server_url matches that integration's registered server, the connection is treated as a catalog connection; otherwise it requires the custom MCP servers capability.
When set, the OAuth flow will update the existing connection in place rather than creating a new one.
OAuth client ID of a client the user registered on the authorization server themselves (e.g. a NetSuite Integration record). Takes precedence over preregistered credentials and Dynamic Client Registration. Cannot be combined with custom_integration_id. On reconnect, omit to reuse the connection's stored credentials, or provide to replace (rotate) them.
1Client secret for oauth_client_id. Omit for public clients (PKCE-only).
1Response
Default Response
OAuth provider authorization URL to open in a browser