Flodesk MCP Server for VS Code CopilotGive VS Code Copilot instant access to 10 tools to Add Subscriber To Segment, Add Subscriber To Workflow, Create Segment, and more
GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
Ask AI about this App Connector for VS Code Copilot
The Flodesk app connector for VS Code Copilot is a standout in the Productivity category — giving your AI agent 10 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Flodesk and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"flodesk-alternative": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 take full control of your email marketing and subscriber workflows through natural conversation.
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.
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
The Flodesk MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 10 Flodesk tools available for VS Code Copilot
When VS Code Copilot connects to Flodesk through Vinkius, your AI agent gets direct access to every tool listed below — spanning subscriber-management, email-campaigns, audience-segmentation, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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
Connect Flodesk to VS Code Copilot via MCP
Follow these steps to wire Flodesk into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using Flodesk
Why Use VS Code Copilot with the Flodesk MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Flodesk through the Model Context Protocol.
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 + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Flodesk MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Example Prompts for Flodesk in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Flodesk immediately.
"List all my Flodesk segments."
"Find subscriber details for 'hello@example.com'."
"Add subscriber 'user@example.com' to the 'Welcome Flow' workflow."
Troubleshooting Flodesk MCP Server with VS Code Copilot
Common issues when connecting Flodesk to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Flodesk + VS Code Copilot FAQ
Common questions about integrating Flodesk MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.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.