Marketing Automation
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.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Flodesk to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Flodesk once
-
Open Connections, choose Add connection, and pick Flodesk.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
Flodesk
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Flodesk to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Flodesk to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Flodesk through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Set up a segment for a launch
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.
-
Sales
Add a new lead to the list
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.
-
Events
Load attendees after a webinar
Paste a registration list and have each attendee created as a Flodesk subscriber, then check the count against the sign-up sheet.
-
Support
Check what a subscriber is receiving
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.
-
Operations
Honor a removal request the same day
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.
-
Marketing
Review workflows and custom fields
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.
Try asking
- “List Flodesk segments and how many subscribers each holds.”
- “Add these three subscribers to the Welcome segment.”
- “Which Flodesk workflows are live right now?”
AI tools
Flodesk tools for your AI agents
18 tools are ready to call through Elaichi's MCP endpoint the moment you connect Flodesk, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Flodesk gets you
6 screens from the product, each doing one job for your Flodesk account.
The agent
Ask about Flodesk segments in plain language.
Answers come from live Flodesk subscribers, segments and workflows, not a stale export.
- segments
- subscribers
- workflows
- custom fields
Ask Elaichi to work across your apps.
List Flodesk segments and how many subscribers each holds.
Add these three subscribers to the Welcome segment.
Which Flodesk workflows are live right now?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Flodesk.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
18 Flodesk tools ready on connect.
Segments, subscribers, workflows, custom fields and webhooks, with no custom code to write.
- List all Flodesk segments
- Get single Flodesk segment by ID
- Create a Flodesk segment
- List all Flodesk subscribers
Toolboxes
Every team gets its own Flodesk toolbox.
Curate one toolbox per team so each sees the Flodesk tools it needs.
- Marketing
- Lifecycle
- Growth
- Sales
Shared connections
Teammates send through Flodesk without the key.
Each Flodesk connection shows who connected it and which teams and members share it.
- Marketing
- Lifecycle
- Growth
- Sales EMEA
Audit log
Every Flodesk call is written down.
When, who, what happened, type and resource, appended for each Flodesk request.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule runs your Flodesk digest.
Fetch subscribers, group them, draft a digest, approve it, post back to Flodesk.
Flodesk digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch segments
Flodesk
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Flodesk
Queued
Collections and dashboards
Flodesk numbers arrive before anyone asks.
Four metrics, 14 days of subscribers created and a team breakdown, refreshed on schedule.
Flodesk health
Refreshed 4 minutes ago · every 15 minutes · from the segments collection
Segments
1,284 ↓ 12%
Subscribers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Segments created
Last 14 days
By team
Share of activity
Marketing 34%
Lifecycle 27%
Growth 21%
Sales EMEA 18%
FAQ
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 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.
Put Flodesk in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.