How to Use the Campaign Monitor MCP in Claude Code

Q: Can Claude Code read Campaign Monitor templates?

Yes. The agent uses the listemailtemplates tool to pull down the metadata for your designs. It displays the names and IDs directly in your terminal session.

Connect Campaign Monitor to Claude Code using this MCP Server. Trigger subscriber updates and pull campaign metrics from your terminal.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Campaign Monitor MCP to Claude Code

Create your Vinkius account to connect Campaign Monitor to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Campaign Monitor with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Fetch Campaign Monitor metrics via MCP Server

You live in the terminal. When marketing needs a quick check on last night's send, you do not need to open a browser. Claude Code runs `list_campaigns` to find the ID. The agent then pipes that ID into `get_campaign_performance`. It spits out the open rates and click stats right in your standard output, letting you get back to your deployment in seconds.

Script subscriber additions

Backend engineers often need to sync user databases with marketing lists. You ask the CLI to read a local CSV and push the records using `add_subscriber`. The agent loops through the rows, formats the payloads, and fires the requests. The MCP connection handles the API interaction entirely headless, making it perfect for quick data migrations.

Map client assets from the CLI

Auditing a massive agency account takes hours by hand. You tell the agent to map the workspace, and it chains `list_clients` with `list_contact_lists`. It dumps the resulting JSON into a formatted local file. You get a complete inventory of every client and their active lists without clicking through dozens of web pages.

Setup guide

Set up Campaign Monitor MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see campaign-monitor-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Campaign Monitor transactions." It will automatically discover and invoke the available Campaign Monitor tools.

Terminal

claude mcp add --transport http campaign-monitor-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Campaign Monitor MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "campaign-monitor-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Campaign Monitor. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Campaign Monitor now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Campaign Monitor MCP in Claude Code

Run the add command with the transport flag set to http. Put all your scope flags before the server name. The configuration saves to your local settings file automatically.

Yes. The agent uses the `list_email_templates` tool to pull down the metadata for your designs. It displays the names and IDs directly in your terminal session.

Yes, it does. You run the CLI headless inside a GitHub Action. The agent pulls campaign performance stats and appends them to your build logs.

The MCP Server passes the HTTP 429 error back to the client. The agent reads the error, waits for the specified timeout, and retries the tool call without crashing your script.

Vinkius hosts this MCP Server in an ephemeral V8 sandbox. Your contact emails, campaign stats, and client names never hit a persistent disk. The data exists only during the active execution window.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript