> For the complete documentation index, see [llms.txt](https://help.genesis.autify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.genesis.autify.com/resources-context/integrations.md).

# Integrations

The **Integrations** subtab, under **Resources and context**, manages MCP server connections and plugins for this workspace. It consists of two sections: **MCP servers** and **Plugins**.

## Prerequisites

| Action                                                               | Required role                       |
| -------------------------------------------------------------------- | ----------------------------------- |
| View MCP connections and plugins                                     | All members                         |
| Add, edit, or delete MCP connections                                 | Admin / Owner, or Workspace Manager |
| Add, edit, or delete Nexus, Aximo, and Slack channel plugin settings | Admin / Owner, or Workspace Manager |

## Accessing the integrations tab

1. On the workspace page, select the **Resources and context** tab.
2. Select the **Integrations** subtab.

<figure><img src="https://1185567431-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmONwRwHy0ZQhls8DWJsO%2Fuploads%2Fgit-blob-167288a5bbd7f074657317463ffed63264c1d3cc%2Fresources-context-integrations-tab.png?alt=media" alt="Screenshot of the Integrations subtab under Resources and context"><figcaption><p>Integrations subtab under Resources and context</p></figcaption></figure>

## MCP servers

Register and manage connections to external MCP (Model Context Protocol) servers used by this workspace. Connections registered here are available as tools from the AI Agent block in workflows.

Each connection card shows the connection name, authentication method (**OAuth** or **API Key / Headers**), server URL, and connection status.

### Adding a connection

1. Click **New connection**.
2. From the preset list, select the app to connect (such as GitHub Production), or select **Custom** to specify any MCP server URL.
3. In **Enter your server details**, fill in the following items.
   * **Name** — Name to identify the connection (for example: JIRA Production).
   * **URL** — Endpoint URL of the MCP server.
   * **Authentication method** — Select **OAuth** or **API Key / Headers** with the radio buttons.
4. Click **Next**.
5. In **Credentials**, enter the following depending on the authentication method you chose.
   * If you chose **OAuth**, you can usually proceed without entering any additional information. Open **Advanced (optional)** and configure the client ID, client secret, token URL, authorization URL, and scopes only when connecting to an MCP server that does not support dynamic registration.
   * If you chose **API Key / Headers**, enter a **Header key** and **Value** (for example: `Authorization: Bearer ...`). You can add additional header rows as needed.
6. Click **Connect & Save**. If you chose **OAuth**, you are then redirected to the MCP server's authentication page to approve access.

{% hint style="warning" %}
For security reasons, MCP connections only support external HTTPS URLs. `http://` URLs, localhost, private IPs, link-local addresses, and other internal addresses cannot be registered. If you cannot connect, specify an HTTPS MCP server URL reachable over the network.
{% endhint %}

{% hint style="info" %}
Registered header values are masked on screen (●●●●●●●●). To change an existing value, delete it once and add it again.
{% endhint %}

{% hint style="info" %}
If an error occurs, check TLS/certificates, authentication headers, and network settings.
{% endhint %}

### Editing a connection

1. Click **Edit MCP connection** <img src="https://1185567431-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmONwRwHy0ZQhls8DWJsO%2Fuploads%2Fgit-blob-20855d75b93db713da7d5708a7ff1ba1bab944ae%2Ficon-lucide-square-pen.svg?alt=media" alt="" data-size="line"> on the connection card you want to edit.
2. Change the **Name**, **URL**, authentication method, or credentials.
3. Click **Connect & Save**.

### Deleting a connection

1. Click **Delete connection** <img src="https://1185567431-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmONwRwHy0ZQhls8DWJsO%2Fuploads%2Fgit-blob-690270a5f4858b1f05ac9c07e6a54d8fa97e21ea%2Ficon-lucide-trash.svg?alt=media" alt="" data-size="line"> on the connection card you want to delete.
2. Click **Delete connection** in the confirmation dialog.

{% hint style="warning" %}
When you delete a connection, blocks in workflows that use it can no longer call the tool. Confirm the impact on workflows before deleting. Specifically, when you delete a connection, workflows that reference it fail pre-run validation (the error "This workflow uses an MCP connection that does not exist in this workspace" appears). Before deleting, either update the MCP connection in the target workflows or remove unused blocks.
{% endhint %}

### Checking connection status

Click the status badge (**Healthy** / **Error** / **Checking…** / **Needs Authorization** / **Unknown**) on a connection card to immediately verify the connection to the MCP server.

| Status              | Description                                                                                                                                                                                                                                                                                  |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Healthy             | Connected successfully.                                                                                                                                                                                                                                                                      |
| Error               | A problem occurred while connecting to the MCP server. Check the following two points and then click the **Error** status badge to retry the connection. Verify the MCP connection URL. Verify that the authentication header (such as `Authorization: Bearer xxx`) is configured correctly. |
| Checking…           | Verifying whether the connection is reachable.                                                                                                                                                                                                                                               |
| Needs Authorization | The OAuth access token has expired and re-authentication is required. Click the status badge to re-run the authentication flow.                                                                                                                                                              |
| Unknown             | Could not determine whether the connection is reachable. Click the **Unknown** status badge to retry the connection.                                                                                                                                                                         |

### Checking available tools

Click **List tools** <img src="https://1185567431-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmONwRwHy0ZQhls8DWJsO%2Fuploads%2Fgit-blob-0d88fb189cde6db143ee290aa12c255d7344f13c%2Ficon-lucide-list.svg?alt=media" alt="" data-size="line"> on a connection card to view the tools provided by the MCP server. Tool name, description, and parameters are listed. You can search the list, confirm how many tools match the current filter, and expand **Input schema** only for the tools whose parameters you want to inspect.

## Plugins

Manage plugins used in this workspace: Autify product integrations (Nexus, Aximo), external services connected at the organization level (Slack), and your personal Google Drive connection.

### Nexus

Connect Autify Nexus so workflows can run its test plans and read results from this project.

1. On the **Nexus** card, click **Connect**.
2. In **Nexus URL**, paste the URL shown with your Nexus API client credentials. Genesis appends the MCP endpoint automatically.
3. In **API token**, enter a token created in Nexus under **Settings → Manage Clients**.
4. Click **Save**.

Once connected, the card shows a health status (**Healthy** / **Error** / **Checking…** / **Unknown**) and the endpoint Genesis connects to. To change the URL or token, click **Edit**. To remove the connection, click **Disconnect**.

### Aximo

Register an Aximo API key so workflows can call Autify Aximo features.

1. On the **Aximo** card, click **Connect**.
2. Enter your Aximo **API key**, then click **Connect**.

{% hint style="info" %}
You can generate an API key from your Aximo app settings.
{% endhint %}

Once connected, the card shows a health status (**Healthy** / **Error** / **Checking…** / **Unknown**). Click **Disconnect** on the card to remove the connection.

### Slack channels for this workspace

Select which Slack channels this workspace's workflows and chat may post to and read from. If Slack is not connected at the organization level, click **Go to organization settings** to set it up. For the organization-level Slack connection procedure, see [Apps](/settings/connection-settings/integrations-hub.md).

### Google Drive

{% hint style="info" %}
The **Google Drive** card only appears when this deployment has Google Drive integration enabled.
{% endhint %}

Connect your personal Google account so the AI can read and edit Google Sheets files you share with this workspace. The connection is personal to your account — any member can connect their own Google account regardless of role.

1. On the **Google Drive** card, click **Connect Google account** and complete the Google sign-in flow.
2. Click **Add files**, then pick one or more spreadsheets from the Google file picker.

Files you add appear under **Files shared with this project**. For each file, toggle **Allow editing** to let the AI write to it (files are read-only by default), or click **Remove** to stop sharing it. A file can be managed by the member who shared it, or by a member with the Admin, Owner, or Workspace Manager role.

Click **Disconnect** on the card to disconnect your Google account. This stops the AI from accessing files you shared with this workspace.

{% hint style="info" %}
The Google file picker runs inside an embedded Google frame, so it needs third-party cookies for `google.com`. If it asks you to sign in even though you already are, allow third-party cookies for this site and try again.
{% endhint %}

## Further reading

* [Resources and context overview](/resources-context/resources-and-context-overview.md)
