Bring Subscriber Management
to Cline
Learn how to connect Flodesk to Cline and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Flodesk MCP Server?
Connect your Flodesk account to any AI agent and take full control of your email marketing and subscriber workflows through natural conversation.
What you can do
- Audience Orchestration — List and manage your complete database of email subscribers, including retrieving detailed metadata and performing search lookups
- Segment Intelligence — Create and manage subscriber segments (lists) programmatically to maintain a high-fidelity organization of your audience
- Automation Control — Monitor your marketing workflows and programmatically add subscribers to automated sequences directly through your agent
- Subscriber Lifecycle — Create or update subscriber profiles and manage their opt-in status to ensure compliance and engagement
- CRM Personalization — Access and manage custom fields to store unique data points for every subscriber in your account
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Flodesk account (Settings > Integrations > API keys)
3. Start managing your email marketing and automation from Claude, Cursor, or any MCP client
No more manual subscriber lookups or complex segment navigation. Your AI acts as your dedicated email marketing and automation coordinator.
Who is this for?
- Content Creators & Influencers — instantly check subscriber growth and manage newsletters using natural language queries
- Marketing Managers — automate lead nurturing by adding new subscribers to specific workflows without leaving your workspace
- SaaS Founders — monitor audience segments and update subscriber details through simple AI commands
Built-in capabilities (10)
Add a subscriber to a segment
Trigger a workflow for a subscriber
Create a new segment
Get details for a segment
Get details for a subscriber
List subscriber custom fields
List all subscriber segments
List all Flodesk subscribers
List all workflows
Requires email. Create or update a subscriber
Why Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Flodesk tool calls without waiting for prompts between steps. Connect 10 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- —
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
- —
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
- —
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
- —
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Flodesk in Cline
Flodesk and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Flodesk to Cline through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Flodesk in Cline
The Flodesk 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cline only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Flodesk for Cline
Every tool call from Cline to the Flodesk MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Flodesk API Key?
Log in to your Flodesk account, navigate to Settings > Integrations > API keys, and click Generate new key.
Can I search for a subscriber by email?
Yes! Use the get_subscriber tool and provide the email address to retrieve their profile, segments, and status.
How do I trigger an automation for a subscriber?
Use the add_subscriber_to_workflow tool by providing the unique workflow_id and the subscriber's ID or email address.
How does Cline connect to MCP servers?
Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
Can Cline run MCP tools without approval?
By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
Does Cline support multiple MCP servers at once?
Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.