Skip to main content
Changes state - verify before retry Starts a hosted OAuth connection flow for an integration and returns a URL — send the user that URL to click and finish connecting there (e.g. logging into Slack). This is NOT a read-only action, though it never handles the user’s actual credentials directly (that happens on the provider’s own hosted login page). Not every adapter supports this — some require pasting an API key directly into the dashboard instead, which isn’t available through this tool. Use list_integrations first to find valid provider_key/adapter_key values.

Parameters

Before you call

  • Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
  • Provide the required parameters: provider_key, adapter_key.

Example MCP request

Send tools/call after your client completes MCP initialization. Replace placeholder values with IDs and inputs from your workspace. For object and array parameters, follow the nested requirements in the parameter description instead of treating an empty value as complete.
The server returns one text content block. Parse content[0].text as JSON when the tool succeeds. See MCP responses and errors for the full envelope and failure behavior.

Verify the result

Confirm the response is not marked isError. Call List Integrations to read the affected resource. Verify that the intended state is visible before making another change.

Retry safety

This tool changes workspace state. After a timeout, read the affected resource before retrying so you do not create duplicate or conflicting changes.