> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Integration Connect Token

> Use the create_integration_connect_token MCP tool on the DialNexa remote MCP server.

<span data-api-safety-label="changes-state"><Badge color="yellow" size="sm" shape="pill">Changes state - verify before retry</Badge></span>

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

| Name           | Type     | Required | Description                                                          |
| -------------- | -------- | -------- | -------------------------------------------------------------------- |
| `provider_key` | `string` | Yes      | The integration provider key, e.g. "slack" — from list\_integrations |
| `adapter_key`  | `string` | Yes      | The specific adapter key for that provider — from list\_integrations |

## 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.

```json theme={null}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_integration_connect_token",
    "arguments": {
      "provider_key": "VALUE",
      "adapter_key": "VALUE"
    }
  }
}
```

The server returns one text content block. Parse `content[0].text` as JSON when the tool succeeds. See [MCP responses and errors](/docs/mcp-tools/errors) for the full envelope and failure behavior.

## Verify the result

Confirm the response is not marked `isError`. Call [List Integrations](/docs/mcp-tools/integrations/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.

## Related MCP tools

* [List Integrations](/docs/mcp-tools/integrations/list-integrations): `list_integrations`

## Related guides

* [Connect to the DialNexa MCP server](/docs/mcp-tools/overview)
* [Integrations MCP tools](/docs/mcp-tools/integrations/overview)
* [MCP responses and errors](/docs/mcp-tools/errors)