> For the complete documentation index, see [llms.txt](https://docs.allmcp.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allmcp.co/documentation/agent-frameworks/flowise.md).

# Flowise

Connect AllMCP to Flowise using the built-in MCP Tool node.

<a href="/pages/uBaUeZYQpupBMd5c1BY0" class="button secondary" data-icon="layer-group">All frameworks</a> <a href="/pages/QJVxDLqxIz5KMCH5afbE" class="button secondary" data-icon="table-cells">Browse providers</a>

***

## Setup

{% stepper %}
{% step %}

#### Add the MCP Tool node

1. Open **Flowise** and create a new flow (or open an existing one)
2. In the node panel, search for **MCP Tool**
3. Drag the **MCP Tool** node onto the canvas
   {% endstep %}

{% step %}

#### Configure the node

Configure the node with these values:

| Field          | Value                       |
| -------------- | --------------------------- |
| **Server URL** | `https://go.allmcp.co/mcp/` |
| **Transport**  | Streamable HTTP             |
| **Headers**    | `X-API-Key: YOUR_API_KEY`   |
| {% endstep %}  |                             |

{% step %}

#### Wire it up

1. Connect the MCP Tool node to an **Agent** node
2. Connect the Agent node to a **Chat Model** node (Claude, OpenAI, etc.)
3. Click **Save** and then **Test**
   {% endstep %}
   {% endstepper %}

***

## Adding headers

In the MCP Tool node, find the **Headers** section and add:

{% code title="Headers" %}

```
Key:   X-API-Key
Value: YOUR_API_KEY
```

{% endcode %}

***

## Multi-user setup

To scope tools to a specific user, append `?user_id=<id>` to the server URL:

{% code title="Server URL" overflow="wrap" %}

```
https://go.allmcp.co/mcp/?user_id=USER_ID
```

{% endcode %}

{% hint style="info" %}
**Passing the user ID.** In Flowise, this is typically done by passing the URL as a variable from an earlier node or from the chat input.
{% endhint %}

***

## Test the connection

Once the flow is configured, send a test message:

```
List available integrations
```

{% hint style="success" %}
The agent should respond with the AllMCP provider catalog — the integrations you can connect.
{% endhint %}

***

## Connecting a provider

Once the flow is live, users can connect their CRM or other tools through the chat:

```
Connect my Bitrix24. My webhook URL is https://portal.bitrix24.ru/rest/1/xxx/
```

```
Connect Google Sheets
```

{% hint style="info" %}
For OAuth providers, the agent returns an authorization URL.
{% endhint %}

***

{% content-ref url="/pages/uBaUeZYQpupBMd5c1BY0" %}
[Overview](/documentation/agent-frameworks/frameworks.md)
{% endcontent-ref %}

{% content-ref url="/pages/QJVxDLqxIz5KMCH5afbE" %}
[All Providers](/documentation/providers/providers.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.allmcp.co/documentation/agent-frameworks/flowise.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.