[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Campaign Monitor API and MCP server

> 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.

Email marketing platform for brands and agencies: single campaigns, subscriber lists and segments, automated journeys, reports and Insights.

## What is the Campaign Monitor API?

Cotlet's Campaign Monitor API exposes 13 endpoints for your own Campaign Monitor account: list subscriber lists, list segments, list subscribers, list campaigns, get a campaign report, list who opened, clicked or did not open, list journeys, get a journey, create a segment from a campaign, create a campaign draft, add a subscriber, send or schedule a campaign and turn a journey on or off. The list_lists endpoint returns returns the subscriber lists of the account. Each endpoint takes simple JSON inputs like cursor, limit or list_id and works both as an operation of the campaign_monitor_read or campaign_monitor_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Marketing & SEO](https://cotlet.dev/integrations/category/marketing-seo.md)
- **Endpoints:** 13 (8 read, 5 write)
- **Updated:** 2026-10-18

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). Cotlet is a hosted MCP server and REST API for Campaign Monitor with 13 endpoints (8 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Campaign Monitor have an official API?

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.

| Task | Campaign Monitor official | Cotlet |
|---|---|---|
| List lists and segments | Yes: v3.3 API | Yes |
| List subscribers by state and add a subscriber | Yes: v3.3 API, paged | Yes |
| Create a draft campaign | Partly: The API takes your content as a URL to hosted HTML | Yes |
| Send or schedule a campaign | Yes: v3.3 API; a future send date schedules it | Yes |
| Read a campaign report and who opened or clicked | Yes: v3.3 reporting endpoints | Yes |
| Create a segment of people who opened or did not open | Yes: Segment rules on a campaign, you build the rule JSON | Yes |
| Read journey stats | Yes: Journey summary and per-email reports | Yes |
| Turn a journey on or off | No: No endpoint; only the switch in the journey designer | Yes |

Sources: [Campaign Monitor API v3.3](https://www.campaignmonitor.com/api/), [Campaign Monitor API: Getting started (authentication)](https://www.campaignmonitor.com/api/v3-3/getting-started/), [Campaign Monitor API: Journeys](https://www.campaignmonitor.com/api/v3-3/journeys/), [Zapier Help: Get started with Campaign Monitor on Zapier](https://help.zapier.com/hc/en-us/articles/8495917875725-How-to-get-started-with-Campaign-Monitor-on-Zapier)

## For AI agents

```text
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.
Cotlet provides a hosted MCP server and REST API for Campaign Monitor: 13 tools (8 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=campaign-monitor, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    campaign_monitor_read, campaign_monitor_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/campaign-monitor, each operation at its own route, e.g. POST /api/v1/campaign-monitor/campaign-drafts
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_lists, list_segments, list_subscribers, list_campaigns, get_campaign_report, list_campaign_activity, list_journeys, get_journey, create_segment_from_campaign, create_campaign_draft, add_subscriber, schedule_campaign, set_journey_status
Confirm      add_subscriber, schedule_campaign, set_journey_status (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/campaign-monitor-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=campaign-monitor, requests Campaign Monitor in the Cotlet console and creates an API key there.
2. The user signs in to Campaign Monitor once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Campaign Monitor for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Campaign Monitor server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Campaign Monitor MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Campaign Monitor in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Campaign Monitor only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Campaign Monitor login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Campaign Monitor's terms; Cotlet is not affiliated with Campaign Monitor.
```

## What can an AI agent do in Campaign Monitor?

Cotlet is best for marketers and agencies on Campaign Monitor who want their AI agent to report on campaigns, re-send to non-openers, add subscribers and pause journeys without running or fixing a server.

- **[Re-send a campaign to people who did not open it](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server/re-engage-non-openers.md)** (runs: weekly): "Take last Tuesday's Autumn sale campaign, make a segment of everyone who did not open it, draft a new email with the subject "Still thinking about it?" and schedule it for Thursday at 9:00." → `list_campaigns`, `get_campaign_report`, `create_segment_from_campaign`, `create_campaign_draft`, `schedule_campaign`
- **[Weekly email campaign report](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server/weekly-campaign-report.md)** (runs: weekly): "Every Monday, report the open rate, click rate, unsubscribes and spam complaints of each campaign I sent last week, name the best one and list the links people clicked." → `list_campaigns`, `get_campaign_report`, `list_campaign_activity`
- **[Turn a journey on or off](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server/turn-journeys-on-and-off.md)** (runs: weekly): "Turn off the Welcome series journey, tell me how many people are waiting in it, and turn it back on when I say so." → `list_journeys`, `get_journey`, `set_journey_status`
- **Add new leads to a list**: "Add the sign-ups from leads.csv to the Newsletter list in Campaign Monitor with their names, and skip anyone already on it." → `list_lists`, `list_subscribers`, `add_subscriber`
- **Draft a newsletter from your HTML**: "Create a draft called November newsletter from newsletter.html, subject "What is new in November", sender Harbor Coffee, to the Customers list without the Unsubscribed segment." → `list_lists`, `list_segments`, `create_campaign_draft`

## Can Campaign Monitor automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Campaign Monitor connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to re-send a campaign to people who did not open it, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/campaign-monitor/campaigns. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/campaign-monitor/campaigns with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Campaign Monitor.

### list_lists

Returns the subscriber lists of the account. Access: read. REST: `GET /api/v1/campaign-monitor/lists`. MCP: `campaign_monitor_read → list_lists`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `cursor` | string | no | Next page cursor from the previous call. |
| `limit` | integer | no | How many items to return per page. |

Returns each list with its ID and name, as in Lists & subscribers. The IDs feed every other tool that takes a list. Needs no role beyond access to the account.

Example response:

```json
{
  "lists": [
    {
      "list_id": "f2a9b7c1d3e44f08a6b5c4d3e2f10987",
      "name": "Customers"
    },
    {
      "list_id": "1c4e8a2b6d9f4073a5b1c8d2e6f30495",
      "name": "Newsletter"
    }
  ],
  "next_cursor": null
}
```

### list_segments

Lists the segments of one list, or of all lists. Access: read. REST: `GET /api/v1/campaign-monitor/segments`. MCP: `campaign_monitor_read → list_segments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list_id` | string | no | Only segments of this list. Leave out for every list. |
| `cursor` | string | no | Next page cursor from the previous call. |
| `limit` | integer | no | How many items to return per page. |

Returns each segment with its ID, title and the list it belongs to. A segment belongs to exactly one list. Use the IDs as recipients in create_campaign_draft.

Example response:

```json
{
  "segments": [
    {
      "segment_id": "9e2b5d8a1c7f4630b4a9d2e5f8c13706",
      "title": "Autumn sale: not opened",
      "list_id": "f2a9b7c1d3e44f08a6b5c4d3e2f10987"
    }
  ],
  "next_cursor": null
}
```

### list_subscribers

Lists the subscribers of a list by state. Access: read. REST: `GET /api/v1/campaign-monitor/lists/{list_id}/subscribers`. MCP: `campaign_monitor_read → list_subscribers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list_id` | string | yes | List ID from list_lists. |
| `state` | string | no | Active, Unconfirmed, Unsubscribed, Bounced or Deleted. Default Active. |
| `joined_since` | string | no | Only subscribers who joined on or after this date, YYYY-MM-DD. |
| `cursor` | string | no | Next page cursor from the previous call. |
| `limit` | integer | no | How many items to return per page. |

Returns email, name, state, join date and custom fields for each subscriber, newest first. Use it to check whether an address is already on the list before add_subscriber.

Example response:

```json
{
  "subscribers": [
    {
      "email": "ana.silva@example.com",
      "name": "Ana Silva",
      "state": "Active",
      "joined": "2026-10-18",
      "custom_fields": {
        "Frequency": "Weekly"
      }
    }
  ],
  "next_cursor": null
}
```

### list_campaigns

Lists sent, scheduled or draft campaigns. Access: read. REST: `GET /api/v1/campaign-monitor/campaigns`. MCP: `campaign_monitor_read → list_campaigns`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | sent, scheduled or draft. Default sent. |
| `sent_from` | string | no | Only campaigns sent on or after this date, YYYY-MM-DD. For status sent. |
| `sent_to` | string | no | Only campaigns sent on or before this date, YYYY-MM-DD. For status sent. |
| `cursor` | string | no | Next page cursor from the previous call. |
| `limit` | integer | no | How many items to return per page. |

Returns ID, name, subject and send date for each campaign, newest first. Sent campaigns come from Campaigns > Sent, the others from Scheduled and Drafts. The IDs feed the report and segment tools.

Example response:

```json
{
  "campaigns": [
    {
      "campaign_id": "a41f7c9e2d8b4e60b3a1c5d7e9f20814",
      "name": "October newsletter",
      "subject": "Five autumn recipes",
      "sent_at": "2026-10-15T09:00:00",
      "status": "sent"
    }
  ],
  "next_cursor": null
}
```

### get_campaign_report

Reads the Snapshot of a sent campaign. Access: read. REST: `GET /api/v1/campaign-monitor/campaigns/{campaign_id}/report`. MCP: `campaign_monitor_read → get_campaign_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | string | yes | Campaign ID from list_campaigns. |

Returns Delivered, Bounced, Opened, Clicked, Unsubscribes, Marked as Spam and Shares. Rates are percentages of Delivered, as on the Snapshot page. Opens are estimates, because Apple Mail Privacy Protection can raise them. Needs the reports permission.

Example response:

```json
{
  "campaign_id": "a41f7c9e2d8b4e60b3a1c5d7e9f20814",
  "name": "October newsletter",
  "sent": 12480,
  "delivered": 12310,
  "bounced": 170,
  "opened_pct": 41.2,
  "clicked_pct": 4.8,
  "unsubscribes_pct": 0.2,
  "spam_pct": 0.01,
  "shares": 38
}
```

### list_campaign_activity

Lists recipients of a sent campaign by what they did. Access: read. REST: `GET /api/v1/campaign-monitor/campaign-activities`. MCP: `campaign_monitor_read → list_campaign_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | string | yes | Campaign ID from list_campaigns. |
| `type` | string | yes | opened, clicked or not_opened. |
| `cursor` | string | no | Next page cursor from the previous call. |
| `limit` | integer | no | How many items to return per page. |

Reads Recipient activity. Rows for clicked include the links the person viewed, as in the Clicks column. not_opened reads the Not opened tab. Needs the reports permission.

Example response:

```json
{
  "recipients": [
    {
      "email": "ana.silva@example.com",
      "clicks": [
        "https://harborcoffee.example/autumn-menu"
      ]
    }
  ],
  "next_cursor": null
}
```

### list_journeys

Lists the journeys of the account. Access: read. REST: `GET /api/v1/campaign-monitor/journeys`. MCP: `campaign_monitor_read → list_journeys`.

No parameters.

Returns each journey with its ID, name and status as Automation shows it. Needs the automation permission.

Example response:

```json
{
  "journeys": [
    {
      "journey_id": "b7d3e9a1c5f84a2e9b6d0c3f1a8e5724",
      "name": "Welcome series",
      "status": "active"
    },
    {
      "journey_id": "3a6c9e2f5b8d4170a2c5e8b1d4f70963",
      "name": "Win-back",
      "status": "paused"
    }
  ]
}
```

### get_journey

Reads the summary and email steps of a journey. Access: read. REST: `GET /api/v1/campaign-monitor/journeys/{journey_id}`. MCP: `campaign_monitor_read → get_journey`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `journey_id` | string | yes | Journey ID from list_journeys. |

Returns the status, the trigger and the left-panel summary: Emails sent, Unique subscribers, average open, click, unsubscribe and bounce rates, and Subscribers waiting while the journey is active. Each email step comes with its own stats.

Example response:

```json
{
  "journey_id": "b7d3e9a1c5f84a2e9b6d0c3f1a8e5724",
  "name": "Welcome series",
  "status": "active",
  "trigger": "Subscriber joins a list",
  "emails_sent": 3980,
  "unique_subscribers": 1650,
  "avg_open_rate_pct": 52.4,
  "avg_click_rate_pct": 7.1,
  "subscribers_waiting": 214,
  "emails": [
    {
      "name": "Welcome",
      "sent": 1650,
      "open_rate_pct": 61.2
    }
  ]
}
```

### create_segment_from_campaign

Creates a segment of people who opened, clicked or did not open a campaign. Access: write. REST: `POST /api/v1/campaign-monitor/campaigns/{campaign_id}/segment-from-campaigns`. MCP: `campaign_monitor_write → create_segment_from_campaign`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | string | yes | Campaign ID from list_campaigns. |
| `audience` | string | yes | opened (Email opened), clicked (Has any link clicked) or not_opened (Email not opened). |
| `list_id` | string | no | List to build the segment on. Required when the campaign went to more than one list. |
| `name` | string | no | Segment name. Renamed after creation in the segment builder. |

Does what Create Segment on the Snapshot page does. Returns the segment ID, which create_campaign_draft takes as recipients. Reaches no one and is deleted with one click in the app, so it does not wait for your OK. A new segment can take a while to calculate, so send to it later.

Example response:

```json
{
  "segment_id": "9e2b5d8a1c7f4630b4a9d2e5f8c13706",
  "name": "Autumn sale: not opened",
  "list_id": "f2a9b7c1d3e44f08a6b5c4d3e2f10987",
  "rule": "Email not opened",
  "source_campaign_id": "c8e1d4a07b3f4a9e8d2c5b6a7f901234"
}
```

### create_campaign_draft

Creates a single campaign in Drafts with subject, sender, recipients and HTML. Access: write. REST: `POST /api/v1/campaign-monitor/campaign-drafts`. MCP: `campaign_monitor_write → create_campaign_draft`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Campaign name. |
| `subject` | string | no | Subject line. |
| `preview_text` | string | no | Preview text next to the subject. |
| `from_name` | string | no | Sender name. |
| `from_email` | string | no | Sender email. |
| `reply_to` | string | no | Optional reply-to address. |
| `list_ids` | array | no | List IDs from list_lists to send to. |
| `segment_ids` | array | no | Segment IDs from list_segments to send to. |
| `html` | string | no | Email HTML, added through Import HTML. Leave out to design it in the app. |

Walks the campaign checklist: Add subject, Add sender, Select recipients and Design. Returns the campaign ID and which checklist items are still open. It needs the create campaigns permission. A draft reaches no one and is deleted in Drafts, so it does not wait for your OK.

Example response:

```json
{
  "campaign_id": "d5b8e1a4c7f94026a3d6b9e2c5f80173",
  "name": "November newsletter",
  "status": "draft",
  "checklist": {
    "subject": "done",
    "sender": "done",
    "recipients": "done",
    "design": "done"
  }
}
```

### add_subscriber

Adds one person to a list. Access: write, asks the user first. REST: `POST /api/v1/campaign-monitor/lists/{list_id}/subscribers`. MCP: `campaign_monitor_write → add_subscriber`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list_id` | string | yes | List ID from list_lists. |
| `email` | string | yes | Email address of the new subscriber. |
| `name` | string | no | Full name. |
| `custom_fields` | object | no | Custom field values by field name, for example {"Frequency": "Weekly"}. |

Returns the subscriber's state on the list. On a list with double opt-in the state is Unconfirmed until the person confirms. The list's own opt-in settings decide which email the new subscriber gets, so the call reaches that person. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "email": "noor.haddad@example.com",
  "list_id": "1c4e8a2b6d9f4073a5b1c8d2e6f30495",
  "state": "Unconfirmed"
}
```

### schedule_campaign

Sends a draft now or schedules it for later. Access: write, asks the user first. REST: `POST /api/v1/campaign-monitor/campaigns/{campaign_id}/schedule`. MCP: `campaign_monitor_write → schedule_campaign`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | string | yes | Campaign ID from list_campaigns. |
| `send_at` | string | yes | now, or a date and time such as 2026-10-29 09:00 in the account's time zone. |
| `confirmation_emails` | array | no | Addresses that get a notification when the send starts. |

Does what Send now or Confirm schedule does. It reads the Assistant first and stops with its issues if the campaign cannot be sent. If the app asks for payment before a send to more than 5 recipients, the call returns payment_required and nothing is sent. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "campaign_id": "d5b8e1a4c7f94026a3d6b9e2c5f80173",
  "status": "scheduled",
  "send_at": "2026-10-29 09:00",
  "recipients": 5460
}
```

### set_journey_status

Moves the on and off switch of a journey. Access: write, asks the user first. REST: `PUT /api/v1/campaign-monitor/journeys/{journey_id}/status`. MCP: `campaign_monitor_write → set_journey_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `journey_id` | string | yes | Journey ID from list_journeys. |
| `state` | string | yes | on or off. |

Needs the automation permission. Turning on needs every step complete and a monthly billing plan; if the switch is disabled the call returns the unfinished steps. While off, new subscribers cannot trigger the journey, and people inside it keep moving but get no emails. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "journey_id": "b7d3e9a1c5f84a2e9b6d0c3f1a8e5724",
  "name": "Welcome series",
  "status": "paused",
  "previous_status": "active",
  "subscribers_waiting": 214
}
```

## How do I connect Campaign Monitor to Claude Code, Codex or Cursor?

Connecting Campaign Monitor takes three steps: sign up, sign in to Campaign Monitor once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Campaign Monitor to your agent.

1. **Create an account** Sign up and add Campaign Monitor in the console. Your API key is there too.

2. **Sign in to Campaign Monitor in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Campaign Monitor there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Campaign Monitor tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Take last Tuesday's Autumn sale campaign, make a segment of everyone who did not open it, draft a new email with the subject "Still thinking about it?" and schedule it for Thursday at 9:00.
```

### Call Campaign Monitor from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/campaign-monitor with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/campaign-monitor/campaign-drafts \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"November newsletter","subject":"What is new in November","from_name":"Harbor Coffee","from_email":"hello@harborcoffee.example","list_ids":["f2a9b7c1d3e44f08a6b5c4d3e2f10987"],"html":"<html><body><h1>November at Harbor Coffee</h1><p>New seasonal menu, from 3 November.</p><p><unsubscribe>Unsubscribe</unsubscribe></p></body></html>"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "campaign_id": "d5b8e1a4c7f94026a3d6b9e2c5f80173",
  "name": "November newsletter",
  "status": "draft",
  "checklist": {
    "subject": "done",
    "sender": "done",
    "recipients": "done",
    "design": "done"
  }
}
```

## Why use Cotlet for Campaign Monitor?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Campaign Monitor yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Campaign Monitor changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Campaign Monitor to Cotlet?

Yes. You sign in to Campaign Monitor yourself, in your own Cloud Browser, and we never save your password. Your agents only get Campaign Monitor once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

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.

**Is this an official Campaign Monitor integration?**

No, Cotlet is independent of Campaign Monitor. Campaign Monitor's own API is too limited for this work. Cotlet works through your own Campaign Monitor account, the way you use Campaign Monitor in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Campaign Monitor in your console: your agents lose access at once and you stay signed in. Signing out of Campaign Monitor in the browser works too, and Reset browser deletes the whole profile.

## Is there a Campaign Monitor MCP server on GitHub?

Yes. Open-source Campaign Monitor MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it an API key, and fix it when something changes. Cotlet hosts the same kind of server for you and keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, add your API key, add it to each MCP client | Sign up, sign in to Campaign Monitor once, add one MCP server or API key |
| When Campaign Monitor changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Campaign Monitor access | An API key or token in a file on your computer, readable by any program you run | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Tools fail until you create a new key or sign in again by hand | Your Cloud Browser keeps you signed in; if Campaign Monitor logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Campaign Monitor changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Campaign Monitor API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Campaign Monitor API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| 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. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Campaign Monitor account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Campaign Monitor yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Campaign Monitor only after you enable it. When Campaign Monitor signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Campaign Monitor, sign out of Campaign Monitor in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Campaign Monitor's terms:** You use your own Campaign Monitor account and stay responsible for following Campaign Monitor's terms. Cotlet is independent and not affiliated with Campaign Monitor. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Campaign Monitor in the console and press Request access. Then you create your API key and connect Campaign Monitor there.

**Do I need to be technical?**

No. You sign in to Campaign Monitor once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Campaign Monitor to Cotlet?**

Yes. You sign in to Campaign Monitor yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Campaign Monitor once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Campaign Monitor sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Campaign Monitor cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Campaign Monitor's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Campaign Monitor sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Campaign Monitor login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Campaign Monitor offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Which Campaign Monitor permissions does my agent need?**

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.

**Can the agent design the email?**

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.

**How long before I can send to a new segment?**

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.

**Can my agent post or send messages in Campaign Monitor without asking me?**

No. Every call to add_subscriber, schedule_campaign or set_journey_status waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_segment_from_campaign, create_campaign_draft runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Campaign Monitor API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/campaign-monitor from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.