Marketing & SEO
Google Search Console
Request indexing, removals, users and index reports for your sites.
15 endpoints
Campaign Monitor cannot turn a journey on or off from outside the app, and its API key is a setup step for a developer. Sign in to Campaign Monitor once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.
Not affiliated with Campaign Monitor.
| What you need | Campaign Monitor's API | GitHub MCP server | Cotlet |
|---|---|---|---|
| Journey switch, agent-ready tools | No | Partly | Yes, 13 tools |
| Acts as you, signed in 24/7 | No | No | Yes, Cloud Browser |
| Fixed for you when Campaign Monitor changes | N/A | No | Yes, tested every 6h |
| Runs with your laptop off | N/A | No | Yes, hosted |
Checked Oct 22, 2026. Sources: Campaign Monitor API v3.3 · Campaign Monitor API: Getting started (authentication) · Campaign Monitor API: Journeys · Zapier Help: Get started with Campaign Monitor on Zapier
AI agents connect over MCP, scripts call the REST API. Both reach the same 13 tools with one API key.
Add Cotlet to your agent once. Campaign Monitor and every other app you connect show up as its tools.
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" {
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
Every tool is an endpoint under /api/v1/campaign-monitor with its own method and path, such as POST /api/v1/campaign-monitor/campaign-drafts, with the same API key. Our open-source repo has ready scripts to start from.
13 tools on your own Campaign Monitor account. Agents call them as operations of the MCP tools campaign_monitor_read and campaign_monitor_write; scripts call each one at its own REST endpoint, with the same inputs and answers.
| Tool | What it does | Access |
|---|---|---|
| list_lists | Returns the subscriber lists of the account. | read |
| list_segments | Lists the segments of one list, or of all lists. | read |
| list_subscribers | Lists the subscribers of a list by state. | read |
| list_campaigns | Lists sent, scheduled or draft campaigns. | read |
| get_campaign_report | Reads the Snapshot of a sent campaign. | read |
| list_campaign_activity | Lists recipients of a sent campaign by what they did. | read |
| list_journeys | Lists the journeys of the account. | read |
| get_journey | Reads the summary and email steps of a journey. | read |
| create_segment_from_campaign | Creates a segment of people who opened, clicked or did not open a campaign. | write |
| create_campaign_draft | Creates a single campaign in Drafts with subject, sender, recipients and HTML. | write |
| add_subscriber | Adds one person to a list. | writeasks first |
| schedule_campaign | Sends a draft now or schedules it for later. | writeasks first |
| set_journey_status | Moves the on and off switch of a journey. | writeasks first |
Scroll the table for all 13 tools.
You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.
One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Campaign Monitor is enabled for agents, so 20 calls a day come to 550 credits.
| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
Campaign Monitor has a full public REST API, v3.3, for lists, subscribers, segments, campaigns, reports and transactional email, and no official MCP server (checked 22 Oct 2026). Any account holder can get an API key in account settings or register an OAuth app. The API cannot create, edit, turn on or turn off a journey.
Sign up free, open Campaign Monitor under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.
No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 13 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.
Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Campaign Monitor yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Campaign Monitor sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.
Not on anything that reaches other people: add_subscriber, schedule_campaign, set_journey_status wait for your OK by default. You can switch that off per tool for scheduled runs.
It works with the permissions of the account you sign in with. Campaign reports need the reports permission, drafts need create campaigns and journeys need automation. Turning a journey on also needs a monthly billing plan, and a send to more than 5 recipients may ask for payment, which the call reports instead of paying.
create_campaign_draft sets the subject, sender and recipients, and takes your HTML through Import HTML. The visual editor stays in Campaign Monitor, so a draft without html keeps an open Design step you finish there.
Campaign Monitor's API docs say to wait about an hour after importing subscribers or changing a segment before sending to it. The agent schedules re-sends with that gap, which is why schedule_campaign takes a send_at.
Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Campaign Monitor changes. Pick Cotlet if you want it hosted and kept working for you.
Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.
Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.
No. Cotlet is independent and not affiliated with Campaign Monitor.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy