Bring Subscriber Management
to Cursor
Learn how to connect Flodesk to Cursor 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 Cursor?
Cursor's Agent mode turns Flodesk into an in-editor superpower. Ask Cursor to generate code using live data from Flodesk and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Flodesk in Cursor
Flodesk and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Flodesk to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.