Compatible with every major AI agent and IDE
What is the Campaign Monitor MCP Server?
Connect your Campaign Monitor account to any AI agent and take full control of your professional email marketing and audience engagement workflows through natural conversation.
What you can do
- Audience Orchestration — List and manage your subscriber lists programmatically, retrieving detailed metadata and health statistics (active, unsubscribed, bounced) in real-time
- Subscriber Lifecycle — Programmatically add or update people in your lists, including managing custom fields and re-subscription status directly from your agent
- Campaign Architecture — Monitor sent and scheduled email campaigns across multiple clients to maintain high-fidelity oversight of your digital outreach
- Performance Intelligence — Access real-time campaign analytics including opens, clicks, and engagement metrics to coordinate your marketing strategy
- Multi-Tenant Visibility — Retrieve complete directories of sub-accounts (clients) and their associated lists to perfectly coordinate agency or enterprise environments
How it works
- Subscribe to this server
- Retrieve your API Key from Campaign Monitor (Account Settings > API Key)
- Start managing your email marketing pipeline from Claude, Cursor, or any MCP client
No more manual scrubbing through subscriber exports or slow UI navigation. Your AI acts as your dedicated email operations and audience coordinator.
Who is this for?
- Marketing Managers — instantly retrieve campaign results and update subscriber segments using natural language commands
- Growth Marketers — automate the ingestion of new leads and monitor list health without leaving your workspace
- Agency Leads — orchestrate email operations across multiple client accounts through simple AI queries
Built-in capabilities (7)
Create or update a subscriber
Get campaign performance
Get subscriber list health
Get profile for a subscriber
List your account clients
List recent email campaigns
List lists for a client
Why VS Code Copilot?
GitHub Copilot Agent mode brings Campaign Monitor data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 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
Campaign Monitor in VS Code Copilot
Campaign Monitor and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Campaign Monitor 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 | 4,000+ 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 Campaign Monitor in VS Code Copilot
The Campaign Monitor 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 7 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
Campaign Monitor for VS Code Copilot
Every tool call from VS Code Copilot to the Campaign Monitor 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 Campaign Monitor API Key?
Log in to your account, click on your profile (top right), navigate to Account Settings > API Key, and copy your unique token.
Can I manage multiple clients via AI?
Yes! The list_clients tool retrieves all sub-accounts, and you can use their IDs to manage lists and campaigns specifically for each client.
Does it support real-time campaign analytics?
The get_campaign_analytics tool retrieves the most current engagement metrics (opens, clicks, unsubscribes) directly from the platform.
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.
Explore More MCP Servers
View all →
Crisp
6 toolsChat with website visitors in real time, manage support conversations, and build a knowledge base that reduces ticket volume.

DevDocs
3 toolsSearch and read developer documentation via DevDocs.io — list libraries, find specific API pages, and retrieve Markdown docs directly from any AI agent.

Stability AI Alternative
7 toolsGenerate and edit high-quality images using Stable Diffusion models directly from your AI agent.

IBGE Serviços de Dados
8 toolsAccess official Brazilian statistics, geographic data, economic classifications (CNAE), and demographic insights directly from IBGE.
