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

# Request Integration Access

> Use the request_integration_access 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>

Requests access to an integration that's currently disabled by admin — posts a notification for the team to review, it does not enable the integration itself. Use list\_integrations first to check whether the tool is actually disabled (this fails if it's already enabled).

## Parameters

| Name            | Type     | Required | Description                                                          |
| --------------- | -------- | -------- | -------------------------------------------------------------------- |
| `tool_key`      | `string` | Yes      | The tool key being requested, e.g. "gmail" — from list\_integrations |
| `usage_context` | `string` | No       | Optional: what the org wants to use this integration for             |

## Before you call

* Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
* Provide the required parameters: `tool_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": "request_integration_access",
    "arguments": {
      "tool_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)