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

# List Integrations

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

<span data-api-safety-label="read-only"><Badge color="gray" size="sm" shape="pill">Read only</Badge></span>

Returns every integration available to the organization — provider/adapter keys, what each does, and current connection status (connected/disconnected/error, with a masked credential hint if connected). Use this first to find valid provider\_key/adapter\_key values before calling any other integration tool.

## Parameters

This tool takes no parameters.

## Before you call

* Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
* This tool has no required arguments.

## 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": "list_integrations",
    "arguments": {}
  }
}
```

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`, parse `content[0].text` as JSON, and verify that returned IDs and workspace data match the request.

## Retry safety

This tool does not change workspace data. Retrying after a transient transport failure is safe.

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