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

# Disconnect Integration

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

<span data-api-safety-label="destructive"><Badge color="red" size="sm" shape="pill">Destructive</Badge></span>

Disconnects an integration. This takes effect immediately — anything currently relying on this connection (agent functions, workflow application nodes) will stop working until it's reconnected. Reversible by reconnecting, but not instantaneous (the user has to go through the connect flow again), so requires confirm: true — only set this after the user has explicitly approved disconnecting this specific integration, never preemptively.

## Parameters

| Name           | Type      | Required | Description                                                                                                 |
| -------------- | --------- | -------- | ----------------------------------------------------------------------------------------------------------- |
| `provider_key` | `string`  | Yes      | The integration provider key, e.g. "slack"                                                                  |
| `adapter_key`  | `string`  | Yes      | The specific adapter key for that provider                                                                  |
| `confirm`      | `boolean` | Yes      | Must be true. Set this only after the user has explicitly approved disconnecting this specific integration. |

## 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`, `confirm`.
* Set `confirm: true` only after the user approves the exact target and action.

## 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": "disconnect_integration",
    "arguments": {
      "provider_key": "VALUE",
      "adapter_key": "VALUE",
      "confirm": true
    }
  }
}
```

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 target is removed or disconnected before reporting completion.

## Retry safety

This tool can remove or disconnect a resource. Confirm the exact target first, and do not retry after an uncertain result until you verify the current state.

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