Flodesk MCP server

What the model can do

Flodesk email marketing: one subscriber by email (status, name, source, segments), segments with their active subscriber counts, and workflows; can add or update a subscriber, add or remove them from segments or workflows, unsubscribe them, and create segments and custom fields.

Reads

• flodesk_subscriberOne Flodesk subscriber by email address: status (active, unsubscribed, bounced…), name, how they joined…
• flodesk_segmentsFlodesk segments (the groups subscribers are sorted into): name, active subscriber count, type and when created.
• flodesk_workflowsFlodesk workflows (automated email sequences): id and name, optionally only active, paused or draft ones.

Acts, when you ask

These change something in Flodesk. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• flodesk_upsert_subscriberAdds a subscriber to Flodesk, or updates the one with that email (name, custom fields), optionally adding them to segments.
• flodesk_add_subscriber_to_segmentsAdds a Flodesk subscriber to one or more segments.
• flodesk_remove_subscriber_from_segmentsRemoves a Flodesk subscriber from one or more segments; they stay subscribed and in their other segments.
• flodesk_unsubscribe_subscriberUnsubscribes a Flodesk subscriber from all email.
• flodesk_add_subscriber_to_workflowEnrols a Flodesk subscriber in a workflow; they then receive its emails.
• flodesk_remove_subscriber_from_workflowRemoves a Flodesk subscriber from a workflow; its remaining emails to them stop.
• flodesk_create_segmentCreates a segment in Flodesk.
• flodesk_create_custom_fieldCreates a custom subscriber field in Flodesk (for example "Favourite colour").

Connect it

First connect Flodesk on Dashboard → Connections, then add Memtro to your client once. The Flodesk tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Flodesk connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Is jo@example.com still subscribed?
• › How did sam@example.com join our list?
• › Which segments is maya@example.com in?
• › How many active subscribers are in the VIP segment?
• › Add maya@example.com to the Workshop waitlist segment

Questions

Is this an official Flodesk MCP server?

No. It is Memtro's MCP server with Memtro's Flodesk connector behind it: the connector reads Flodesk through its API with the credentials you connect on Dashboard → Connections, and Flodesk publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Flodesk?

Only when you ask, and only what it has been granted: add or update a subscriber, optionally into segments (may email them); add a subscriber to segments (may start segment workflows); remove a subscriber from segments; unsubscribe a subscriber from all email; add a subscriber to a workflow (they receive its emails); remove a subscriber from a workflow; create a segment; create a custom subscriber field. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Marketing automation

• ActiveCampaign MCP server
• Brevo MCP server
• Customer.io MCP server
• Marketo Engage MCP server
• Account Engagement (Pardot) MCP server
• Mailchimp MCP server