Bring Subscriber Management
to VS Code Copilot
Learn how to connect Flodesk to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Flodesk data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Flodesk in VS Code Copilot
Flodesk and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Flodesk to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.