> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/mcp-integration.md).

# MCP Integration

The IZ MCP server lets an AI assistant use IZ Suite tools with the permissions of an access token. The **MCP integration** tab builds the configuration for your assistant, with your server's address already filled in.

Open it from **Administration** → **Global Settings** → **MCP integration** in the sidebar.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FvgWLF8lrrq8Q6NrCtJs3%2Fv2-gs-mcp.png?alt=media&amp;token=1213444f-0ca6-4887-bee9-d435542c75e7" alt="MCP integration tab with the four setup steps, the HTTP configuration and the access token links"><figcaption><p>MCP integration</p></figcaption></figure>

{% hint style="warning" %}
You need a role that can view global settings to open this tab.
{% endhint %}

## Connect an Assistant

{% stepper %}
{% step %}

### Choose How the Assistant Connects

Under **1. Choose how the assistant connects**, pick:

* **HTTP (recommended)**: the assistant connects to your IZ Suite server directly.
* **STDIO (local helper)**: the assistant runs a local helper through npm. Use it for clients that only support local servers.
  {% endstep %}

{% step %}

### Choose Your Assistant

Under **2. Choose your assistant**, pick **VS Code** or **Cursor**. **Claude Desktop** is available with **STDIO (local helper)** only.
{% endstep %}

{% step %}

### Add the Configuration

Under **3. Add this configuration**, copy the configuration and paste it:

| Assistant          | Where to paste it                                                                                         |
| ------------------ | --------------------------------------------------------------------------------------------------------- |
| **VS Code**        | Your VS Code MCP settings (`mcp.json`).                                                                   |
| **Cursor**         | Cursor → Settings → MCP.                                                                                  |
| **Claude Desktop** | Claude Desktop → Settings → Developer → Edit config (under `mcpServers` in `claude_desktop_config.json`). |

Replace `##ACCESS_TOKEN##` with the token from the next step, then restart the assistant.
{% endstep %}

{% step %}

### Create a Dedicated Access Token

Under **4. Create a dedicated access token**:

1. Click **Create a role for the assistant** and create a role with only the permissions the MCP tools need. **Permissions each MCP tool needs** lists them.
2. Click **Create your access token** and create a token that carries that role.
3. Copy the token. It is shown only once.

**Review existing access tokens** opens the list of tokens in the workspace.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
This tab does not test the connection. The connection works when your assistant lists the IZ tools.
{% endhint %}

{% hint style="danger" %}
The access token gives the assistant the permissions of its role. Give the assistant a dedicated token with only the roles it needs, and never share the token.
{% endhint %}

## Configuration Samples

Replace `https://izsuite.example.com` with your IZ Suite address (in a multi-tenant installation, your tenant's address) and the token value with the token you created.

{% tabs %}
{% tab title="HTTP" %}
{% code title="mcp.json (VS Code or Cursor)" %}

```json
{
  "iz-suite-mcp-server": {
    "url": "https://izsuite.example.com/mcp",
    "type": "http",
    "headers": {
      "x-iz-access-token": "<token generated in IZ Suite>"
    }
  }
}
```

{% endcode %}

Every request carries a header: `x-iz-access-token` with your token.

{% hint style="info" %}
Assistant configurations created before release 26.4.2 send the earlier header names. IZ Suite still accepts their token header and ignores the old service URL header, so they keep working; new configurations need only `x-iz-access-token`.
{% endhint %}
{% endtab %}

{% tab title="STDIO" %}
{% code title="VS Code, Cursor or Claude Desktop" %}

```json
{
  "iz-scan-mcp-server": {
    "command": "npx",
    "args": [
      "-y",
      "--registry=https://npm.integralzone.com",
      "iz-scan-mcp",
      "--accesstoken",
      "<token generated in IZ Suite>",
      "--serverurl",
      "https://izsuite.example.com"
    ],
    "type": "stdio"
  }
}
```

{% endcode %}

The helper runs through `npx`, so the machine that runs the assistant needs npm. `--serverurl` must be your IZ Suite address.
{% endtab %}
{% endtabs %}

## Next Steps

* [Roles](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/roles.md): create the role that limits what the assistant can do.
* [Access Tokens](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/access-tokens.md): review the tokens in your workspace.
* [Security Credentials](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/my-account/security-credentials.md): create your own access token.
* [Global Settings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings.md): the other configuration screens.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/mcp-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
