# MCP

### **1. Configuring an MCP Connection**

In the **Integrations** page, you’ll now see a new integration type called **MCP**.

When you open this integration type, the platform displays all MCP connections currently defined in the environment. The MCP integration behaves similarly to existing integrations such as REST—however, MCP connections follow a fixed structure aligned with the MCP standard.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2Fonkx8f7Vj9APUSEQF0Ix%2Fimage.png?alt=media&#x26;token=0117bf1e-6d97-4040-bc36-215d144c5e2d" alt=""><figcaption></figcaption></figure>

#### **Creating a New MCP Connection**

1. Click **Create Connection**.
2. Provide a **Connection Name** (e.g., `Test Demo`).
3. Click **Save**.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FGOohFiXfhNeTHxaMAiMQ%2Fimage.png?alt=media&#x26;token=8f6ca137-4aea-4fc4-90cd-bdd0f01829d6" alt=""><figcaption></figcaption></figure>

Once saved, the platform prompts for additional required configuration:

#### **MCP Server Settings with No Authentication Type**

You must specify:

* **MCP Endpoint URL** – The base URL of your MCP server [Setup MCP](https://docs.ixhello.com/ixhc2/general/tutorials/mcp-connection-setup)
* **Authentication Type** – Select one of the supported authentication methods (No Authentication)

Click **Save** to finalize.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FuqLTefn77ME1RJTYdeDh%2Fimage.png?alt=media&#x26;token=98d627de-863e-4832-84ce-745f3ae8b8ad" alt=""><figcaption></figcaption></figure>

#### **MCP Server Settings with Oauth Authentication Type**

You must specify:

* **MCP Endpoint URL** – The base URL of your MCP server [Setup MCP](https://docs.ixhello.com/ixhc2/general/tutorials/mcp-connection-setup)
* **Authentication Type** – Select one of the supported Oauth authentication type
* You’ll now see a new list of MCP servers retrieved from <https://registry.modelcontextprotocol.io/>&#x20;

When you select an MCP server that supports OAuth, the system automatically initiates the OAuth flow. For example, when I choose the *Lona Trading Strategy Platform*, I’m redirected to its authentication page. If you are already logged in, you'll immediately redirected back, and a **new connection** appears in the list—created automatically.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2Fvkn0ZoNEoozme3XqBD2g%2Fimage.png?alt=media&#x26;token=2533bcaa-13f5-41be-a87d-916c4f4ccc8a" alt=""><figcaption></figcaption></figure>

Opening this new connection reveals that both methods were added automatically.\
In the **Edit** view, you’ll notice that all required fields are already filled in:

* Authentication type: **OAuth**
* Client ID: preconfigured
* Other necessary connection details: auto‑populated

#### **Using the Connection in a Flow for Oauth**

Back in the Flows page:\
You can drag a **Tools** node onto the canvas and open the MCP Connections list, the newly created connection appears there. Selecting it displays all the tools provided by that MCP server, ready to use in your flow.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FmoDkVZ3F71BvlEtvPAPo%2Fimage.png?alt=media&#x26;token=17004d88-0e46-4bb9-b415-572f82bb6f11" alt=""><figcaption></figcaption></figure>

Select the desired MCP connection, and the available tools will appear in a drop-down menu. Choose the necessary tool from the list.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FgwuwFhnnUDtzXKx4CuV0%2Fimage.png?alt=media&#x26;token=ff74cfca-f84c-42da-aa7a-08b3792ae1ab" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FEBwbkVOINfpckSRQnulI%2Fimage.png?alt=media&#x26;token=111fdaa1-00ab-4f0c-86c1-a22f0c75befe" alt=""><figcaption></figcaption></figure>

#### **Auto‑Generated Methods**

After saving, the platform automatically generates two fixed methods for every MCP connection:

* **List Tools**
* **Execute Tool**

These methods are used internally by system orchestration layer to discover and invoke MCP tools during runtime.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2F6ayFvlLVQZRJgwAzR0Xl%2Fimage.png?alt=media&#x26;token=fc0e10a3-8b79-4c62-8faf-efecf8161211" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Note**: Users **cannot** create additional, or modify the auto-generated methods for MCP connections.
{% endhint %}

***

### **2. Using an MCP-Connection in a Flow**

{% hint style="info" %}
Refer to [MCP Connection Setup](https://docs.ixhello.com/ixhc2/general/tutorials/mcp-connection-setup) Tutorial for more details.
{% endhint %}

Open any flow in the **Flow Designer**. You will notice a new node type called **Tools**.

#### **Adding an MCP Tools Node**

1. Drag the **Tools** node onto the canvas.
2. Create a new flow or select one of the previously configured MCP connections

Once selected, iX Hello Customer v2 automatically executes the MCP **List Tools** method behind the scenes. The tool list returned by the MCP server is then displayed in the UI.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2Fm5z3bR3q03bZoEVeAcLj%2Fimage.png?alt=media&#x26;token=d4f15b4d-6886-4030-9863-d19bb1a8e58e" alt=""><figcaption></figcaption></figure>

#### **Selecting Tools**

* You can choose one or more tools exposed by the MCP server.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FngiknYfslpTsyn66Que6%2Fimage.png?alt=media&#x26;token=59bf2a7d-e4ec-480f-b53c-80718ccde7b1" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FLqJMSV2YHkqiww5RljW7%2Fimage.png?alt=media&#x26;token=201ff2e9-d155-415d-8b02-fe884268d259" alt=""><figcaption></figcaption></figure>

* These tools can then be attached to an **Agent Node**.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FNVKAAwOI1davMSgwXduU%2Fimage.png?alt=media&#x26;token=c4a1aa2f-995a-4b07-8001-bf534c9d920d" alt=""><figcaption></figcaption></figure>

This gives the agent access to those capabilities during runtime.

#### **Using Multiple MCP-Connections**

An Agent Node can aggregate tools from **multiple MCP connections**.\
The system allows mixing tools from different servers.

{% hint style="warning" %}
**Note**: A maximum of **5 tools** can currently be added per Tools Node.
{% endhint %}

With this, the MCP capabilities are now attached to the agent.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FU6gI7qsEoo0ZvG6C6CrQ%2Fimage.png?alt=media&#x26;token=200b0c34-b036-440a-81d0-da4a1f293084" alt=""><figcaption></figcaption></figure>