# Flodesk MCP connector The Flodesk connector brings your Flodesk subscribers, segments, workflows and custom fields to Claude, ChatGPT, Cursor and other AI clients, so your team can ask about and update your email list in plain language, within each person's own Flodesk access. Source: https://elaichi.ai/connectors/flodesk/ ## Facts | | | | --- | --- | | Application | Flodesk | | Category | Marketing Automation | | AI tools | 18 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Flodesk is connected - List Flodesk segments and how many subscribers each holds. - Add these three subscribers to the Welcome segment. - Which Flodesk workflows are live right now? ## Connect Flodesk in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Flodesk. 2. Optionally set Share with, then press Connect. 3. Paste a Flodesk API key. One person generates a token in Flodesk and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Flodesk tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Flodesk to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Flodesk to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Flodesk to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Flodesk to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Flodesk tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Flodesk through Elaichi ### Set up a segment for a launch Marketing. Ask for a new Flodesk segment named for the campaign you are about to run, pick its color from the ones already in your account, and have it ready before the emails are written. ### Add a new lead to the list Sales. After a call, give the name and email address and have the person added as a Flodesk subscriber, so they start receiving the right emails without anyone opening Flodesk. ### Load attendees after a webinar Events. Paste a registration list and have each attendee created as a Flodesk subscriber, then check the count against the sign-up sheet. ### Check what a subscriber is receiving Support. Look up a subscriber by their record and see what Flodesk holds for them when someone writes in asking why they got, or did not get, an email. ### Honor a removal request the same day Operations. When someone asks to be taken off your emails, find their Flodesk subscriber record and remove it, with the action recorded in the audit log. ### Review workflows and custom fields Marketing. Ask which Flodesk workflows are live and which custom fields exist before a campaign, and add a missing field, such as company or plan, so the next emails can use it. ## Frequently asked questions ### How do I connect Flodesk to Claude? First, connect Flodesk in Elaichi by pasting the API key from your Flodesk account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Flodesk is available in Claude. ### Does Flodesk work with ChatGPT and Cursor as well as Claude? Yes. Once Flodesk is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Flodesk once and use it from every client your team prefers. ### What can an AI agent actually do with my Flodesk data? With Flodesk connected, an AI agent can look up subscribers, add new ones, and remove a subscriber when someone asks to be taken off your list. It can list your segments and create a new one, list and create workflows, and add custom fields such as company or plan. It can also set up and manage the webhooks that tell other tools when something happens in Flodesk. ### Does connecting Flodesk give the AI everything in my account? No more than the person who signed in can already reach. Every call to Flodesk runs as that person, so the AI sees the subscribers, segments and workflows their Flodesk access allows and nothing beyond it. Elaichi can narrow that further, for example to read-only, but it can never widen access past what Flodesk itself grants. ### Can my team share one Flodesk connection? Yes. One person connects Flodesk in Elaichi with the API key and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so every change to a subscriber or segment in Flodesk is logged under the name of the person who made it. ### Can I stop an agent from deleting or changing things in Flodesk? Yes. Restrictions in Elaichi work per action, so you can allow looking up and adding Flodesk subscribers while blocking deletion of subscribers or workflows. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it. ### What happens to a Flodesk connection when someone leaves? When you offboard someone in Elaichi, their access to Flodesk through every AI client ends at once. A Flodesk connection shared with the team keeps working for everyone else. If you want to remove Flodesk entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time. ## All 18 Flodesk tools Every tool below is callable through https://api.elaichi.ai/mcp once Flodesk is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Flodesk segments** (List). List all segments in Flodesk. Returns id, name, total_active_subscribers, created_at, and color for each segment. - **Get single Flodesk segment by ID** (Get). Get details of a specific segment in Flodesk using id. Returns id, name, total_active_subscribers, created_at, and color fields in the response. - **Create a Flodesk segment** (Create). Create a segment in Flodesk. Requires name and color. Returns id, name, total_active_subscribers, created_at, and color in the response. - **List all Flodesk subscribers** (List). List all subscribers in Flodesk. Returns each subscriber's id, status, email, first_name, last_name, segments, custom_fields, optin_ip, optin_timestamp, and created_at. - **Get single Flodesk subscriber by ID** (Get). Get a specific subscriber in Flodesk using id_or_email. Returns id, status, email, source, name fields, segments, custom_fields, optin_ip, optin_timestamp, and created_at. - **Create a Flodesk subscriber** (Create). Create or update a subscriber in Flodesk using email or id. Returns subscriber details including id, status, email, source, first_name, last_name, segments, custom_fields, optin_ip, optin_timestamp, and created_at. - **Delete a Flodesk subscriber by ID** (Delete). Remove a subscriber from segments in Flodesk. Requires id_or_email and segment_ids. Returns subscriber details including id, status, email, segments, and custom_fields. - **List all Flodesk segment colors** (List). List all available segment colors in Flodesk. Returns an array of color strings representing the available segment color options. - **List all Flodesk workflows** (List). List workflows in Flodesk. Returns an array of workflows with fields id and name for each workflow. - **Create a Flodesk workflow** (Create). Add a subscriber to a workflow in Flodesk. Requires id for the workflow and either subscriber id or email. Subscribers must not be active or in abandoned cart workflows. Returns subscriber details and workflow status. - **Delete a Flodesk workflow by ID** (Delete). Remove a subscriber from a specific workflow in Flodesk. Requires workflow_id and id. Returns 204 on success or 404 if not found. - **List all Flodesk custom fields** (List). List all custom fields in Flodesk. Returns key and label for each field. - **Create a Flodesk custom field** (Create). Create a custom field in Flodesk using the required parameter label. Returns details of the created custom field, including its id, label, and metadata. - **List all Flodesk webhooks** (List). List all webhooks in Flodesk. Returns webhook details including id, event type, target URL, and creation timestamp. - **Get single Flodesk webhook by ID** (Get). Get details of a specific webhook in Flodesk using id. Returns webhook configuration fields including the event type, target URL, and status. - **Create a Flodesk webhook** (Create). Create a webhook in Flodesk. Requires name, post_url, and events. Returns id, post_url, events, and created_at fields in the response. - **Update a Flodesk webhook by ID** (Update). Update a webhook in Flodesk using id. Returns id, post_url, events, and created_at fields describing the updated webhook configuration. - **Delete a Flodesk webhook by ID** (Delete). Delete a webhook in Flodesk using id. Returns 204 on successful deletion or 404 if the specified webhook is not found.