How do I add a new subscriber to a specific segment using the agent?

You can use the 'add_to_segment' tool. Provide the subscriber's email or ID and the specific Segment ID. The agent will immediately associate the contact with that segment in your Flodesk account.

Can I trigger an automated email sequence for a user?

Yes! The 'trigger_workflow' tool allows you to start a subscriber on any of your active Flodesk workflows. Simply provide the Workflow ID and the subscriber's email address.

How do I check if a contact is active or unsubscribed?

Use the 'get_subscriber' tool and provide the contact's email address. The agent will retrieve the profile details, including their current status (e.g., 'active', 'unsubscribed', or 'bounced').

Flodesk MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: Flodesk
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Flodesk through Vinkius, pass the Edge URL in the `mcps` parameter and every Flodesk tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Flodesk Specialist",
    goal="Help users interact with Flodesk effectively",
    backstory=(
        "You are an expert at leveraging Flodesk tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Flodesk "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Flodesk MCP Server

Connect your Flodesk account to any AI agent and automate your email marketing and audience management through the Model Context Protocol (MCP). Flodesk is designed for creators and businesses that want to build stunning emails and automate their sales funnels with ease. Now, you can manage your subscribers, organize your segments, and trigger automated workflows directly through natural conversation.

When paired with CrewAI, Flodesk becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Flodesk tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Subscriber Management — List all email subscribers, fetch detailed profile data, and create or update subscriber records instantly.
Audience Segmentation — Access and list your segments, and add subscribers to specific groups to ensure targeted messaging.
Workflow Automation — List your automated email sequences and trigger specific workflows for new or existing subscribers.
Opt-out Handling — Unsubscribe users directly through the agent to maintain a clean and compliant mailing list.
Custom Data Fields — List and create custom subscriber fields to store specific metadata (e.g., interests, purchase history).
Form Oversight — Retrieve a list of all your opt-in forms to monitor where your audience is coming from.
Account Insights — Fetch your Flodesk account metadata to ensure your agent has the correct context for your branding.

The Flodesk MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Flodesk to CrewAI via MCP

Follow these steps to integrate the Flodesk MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Flodesk

Why Use CrewAI with the Flodesk MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Flodesk through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Flodesk + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Flodesk MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Flodesk for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Flodesk, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Flodesk tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Flodesk against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Flodesk MCP Tools for CrewAI (12)

These 12 tools become available when you connect Flodesk to CrewAI via MCP:

add_to_segment

Add subscriber to segment

create_custom_field

Create custom field

create_subscriber

Add a subscriber

get_account_details

Get account info

get_subscriber

Get subscriber details

list_custom_fields

List custom subscriber fields

list_forms

List opt-in forms

list_segments

List segments

list_subscribers

List email subscribers

list_workflows

List automation workflows

trigger_workflow

Start workflow for user

unsubscribe_subscriber

Unsubscribe a user

Example Prompts for Flodesk in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Flodesk immediately.

"List my 10 most recent email subscribers."

"Add 'hello@newlead.com' to my 'Welcome' segment and trigger the 'Onboarding' workflow."

"Show me all my active automation workflows."

Troubleshooting Flodesk MCP Server with CrewAI

Common issues when connecting Flodesk to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Flodesk + CrewAI FAQ

Common questions about integrating Flodesk MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.