> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.flowella.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect AI assistants to Flowella with MCP

> Connect Claude, ChatGPT, Cursor and other AI assistants to your Flowella organisation through the Flowella MCP server, and review or revoke their access.

The Flowella MCP server lets AI assistants that support the Model Context Protocol (MCP), such as Claude, ChatGPT, Cursor and Claude Code, work with your Flowella organisation. Ask an assistant to list your templates, check a Flow, look up a conversation or report on usage. If you approve write access, it can also draft and submit templates, send approved templates and manage Flows, contacts and webhooks for you.

The assistant works through the [Flowella REST API](https://knowledge.flowella.io/api-reference/introduction.md), so the same rules apply as for any integration: the 24-hour window, opt-outs and your plan's usage all still count.

## Before you start

* Your AI assistant supports remote MCP servers with sign-in. Claude, ChatGPT, Cursor and Claude Code all do.
* Your role decides what the assistant can do. An **Owner** or **Admin** can approve read and write access. A **Member** can connect with read-only access.

## Connect an assistant

The server address is:

```text theme={null}
https://mcp.flowella.io/mcp
```

> [tab] Claude and ChatGPT
>
> Add a custom connector in your assistant's settings and paste the server address. The assistant registers itself with Flowella, so you don't need a client ID or secret.

> [tab] Cursor and Claude Code
>
> Add Flowella to your MCP configuration:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "flowella": {
>       "url": "https://mcp.flowella.io/mcp"
>     }
>   }
> }
> ```

The first time the assistant connects, it opens the Flowella consent screen in your browser. Sign in if you are asked to.

## Approve access

On the consent screen:

1. Under **Choose organization**, pick the organisation the assistant can use. Each connection works with one organisation only.
2. Check the **Requested scopes**: what the assistant can read and change.
3. Select **Allow access**, or **Deny** to cancel.

If you are a Member, the screen notes that the connection is read-only, and any write scopes are not granted. An Owner or Admin can connect the same assistant with write access.

## What the assistant does with your approval

* **Reading** works straight away: channels, templates, Flows, conversations, contacts, usage and webhooks.
* **Sending, changing and deleting** need write scopes, and the assistant must confirm each action before it runs. It can also preview a request without running it.
* A template only reaches contacts after Meta approves it. An assistant can create and submit a draft, but not skip approval.
* Messages an assistant sends count toward your usage like any other send.

## Review and revoke access

Owners and Admins can see every assistant and app connected to the organisation, and revoke any of them.

1. Go to **Settings**, then select **AI assistants** in the **Developer** group.

2. Find the assistant in the list:

   | Column | What it shows |
   | - | - |
   | **App** | The assistant or app's name, with its client ID below. |
   | **Scopes** | The scopes it was granted. |
   | **Installed** | When it was first approved. |
   | **Last token** | When it last got an access token, or **No token yet**. |
   | **Actions** | **Revoke**, or a **Revoked** badge. |

3. Select **Revoke** and confirm **Revoke this install? Existing tokens stop working.**

The assistant loses access at once. To connect it again, approve it again on the consent screen.

## Read-only access with an API key

For scripts and tools that cannot open a sign-in page, Flowella also has a read-only MCP server that accepts an organisation API key:

```text theme={null}
https://app.flowella.io/api/mcp
```

Send the key in an `Authorization: Bearer` header. This server can list your channels, templates and Flows and read a template or Flow, but it cannot change anything. Revoke the key under [API keys](https://knowledge.flowella.io/settings/api-keys.md) to stop access.

## Related

> [card] [API keys](https://knowledge.flowella.io/settings/api-keys.md)
>
> Create and revoke keys for the REST API.

> [card] [Developer apps](https://knowledge.flowella.io/settings/developer-apps.md)
>
> Register OAuth apps that other organisations can install.

> [card] [Flowella REST API](https://knowledge.flowella.io/api-reference/introduction.md)
>
> The API the MCP server calls on your behalf.

> [card] [Developer changelog](https://knowledge.flowella.io/api-reference/changelog.md)
>
> Changes to the API, webhooks, OAuth and MCP.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.