Flodesk MCP connector
The Flodesk connector brings your Flodesk subscribers, segments, workflows and custom fields to Claude, ChatGPT, Cursor, Microsoft Copilot 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.
- Connects with an API key
- Free 14-day trial
- No credit card
List Flodesk segments and how many subscribers each holds.
Working in Flodesk with Elaichi
-
List all Flodesk segments
-
Get single Flodesk segment by ID
-
List all Flodesk subscribers
How to connect Flodesk to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Flodesk MCP connector for 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.
Flodesk MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Flodesk MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Flodesk MCP connector for 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.
Flodesk MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Flodesk through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Flodesk is logged.
-
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?”
What connecting Flodesk gets you
6 screens from Elaichi, each doing one job for your Flodesk account.
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, Cursor or Microsoft Copilot
The agent
Ask about Flodesk segments in plain language.
Answers come from live Flodesk subscribers, segments and workflows, not a stale export.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Flodesk.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
18 Flodesk tools ready on connect.
Segments, subscribers, workflows, custom fields and webhooks, with no custom code to write.
Toolboxes
Every team gets its own Flodesk toolbox.
Curate one toolbox per team so each sees the Flodesk tools it needs.
Shared connections
Teammates send through Flodesk without the key.
Each Flodesk connection shows who connected it and which teams and members share it.
Audit log
Every Flodesk call is written down.
When, who, what happened, type and resource, appended for each Flodesk request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Flodesk digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Flodesk
Queued
Automations
A schedule runs your Flodesk digest.
Fetch subscribers, group them, draft a digest, approve it, post back to Flodesk.
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%
Collections and dashboards
Flodesk numbers arrive before anyone asks.
Four metrics, 14 days of subscribers created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Flodesk
All three can connect Flodesk to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Flodesk tools | Allow or restrict single Flodesk tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Flodesk call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deletion of subscribers or workflows. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client at the same time.
Does the Flodesk MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Flodesk is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Flodesk?
Yes. Both let Claude, ChatGPT or Cursor use Flodesk. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Flodesk call.
How is Elaichi different from Composio for Flodesk?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Flodesk: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Flodesk in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot