[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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 status Does Campaign Monitor have an API or MCP server?

> Campaign Monitor has a public API with a key from Account Settings, list webhooks and Zapier and Make apps; no MCP server was found (checked 20 Nov 2026). Cotlet API & MCP access score: 4 out of 5. What exists instead, with sources.

Source: https://cotlet.dev/api-status/campaign-monitor

Campaign Monitor has a public API as of 20 November 2026, and its docs say: "You can get your API key from the Account Settings page when logged into your Campaign Monitor account." Campaign Monitor offers list webhooks for subscribe, update and deactivate events, managed through the API, and exports subscriber lists as CSV. Its Zapier and Make apps have triggers and actions. No Campaign Monitor MCP server was found.

**Cotlet API & MCP access score: 4 out of 5.** A Campaign Monitor team with a developer can connect lists and subscribers to its own software through the API, webhooks, Zapier or Make. No route from Campaign Monitor for ChatGPT or Claude to work in an account was found.

Checked 20 Nov 2026 ·[How Cotlet scores](#how-cotlet-scores)·[Report an inaccuracy](mailto:contact@cotlet.dev?subject=Campaign%20Monitor%20API%20status)

Cotlet publishes this page as an independent assessment. Cotlet is not affiliated with, endorsed by or sponsored by Campaign Monitor. Campaign Monitor is a trademark of its owner. If Campaign Monitor's own tools cover what you need, use them first.

Campaign Monitor API & MCP report

4/5

Cotlet API & MCP access score 7/10 points

Public API

3/3

MCP server

0/3

Zapier · Make · n8n

2/2

Webhooks

1/1

Data export

1/1

Checked

20 Nov 2026

[Report an inaccuracy](mailto:contact@cotlet.dev?subject=Campaign%20Monitor%20API%20status) [How we score](#how-cotlet-scores)

Public API

Public

3 of 3

MCP server

None

0 of 3

Zapier · Make · n8n

Zapier, Make

2 of 2

Webhooks

Lists

1 of 1

Data export

CSV

1 of 1

On this page

1. [01 At a glance](#at-a-glance)
2. [02 Public API](#public-api)
3. [03 MCP server](#mcp-server)
4. [04 Webhooks](#webhooks)
5. [05 Zapier, Make, n8n](#automation)
6. [06 Routes](#routes)
7. [07 How Cotlet scores](#how-cotlet-scores)
8. [08 Sources](#sources)

01 · At a glance

## Campaign Monitor API & MCP access at a glance

__Campaign Monitor API & MCP access on 20 Nov 2026 7 of 10 points__
| Check | Points | Finding | Source |
| ------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| Public API for businesses | 3 / 3 | Yes. A public API with a key from Account Settings, or OAuth | [\[1\]](#source-1) |
| Official MCP server | 0 / 3 | No Campaign Monitor MCP server found on its site or in the MCP Registry; registry entries come from other publishers | [\[2\]](#source-2) |
| Zapier, Make, n8n | 2 / 2 | Zapier and Make: apps with triggers and actions such as adding a subscriber. No app found on n8n | [\[4\]](#source-4)[\[5\]](#source-5) |
| Webhooks | 1 / 1 | List webhooks for subscribe, update and deactivate events, set up through the API | [\[3\]](#source-3) |
| Data export | 1 / 1 | Subscriber lists export as CSV or tab delimited text | [\[6\]](#source-6) |

One more fact that earns no points: Campaign Monitor's API docs prefer OAuth for apps, and the API key is the simpler path for your own scripts ([Campaign Monitor API v3.3: Getting started](https://www.campaignmonitor.com/api/v3-3/getting-started/)).

02 · Public API

## Does Campaign Monitor have a public API?

Yes

Campaign Monitor has a public API, version 3.3, that an account authorizes with an API key or OAuth. Its docs say: "You can get your API key from the Account Settings page when logged into your Campaign Monitor account." No plan requirement for API access was stated on 20 November 2026.

[ Source \[1\] · Campaign Monitor API v3.3: Getting started ](#source-1)

03 · MCP server

## Does Campaign Monitor have an MCP server?

None found

Campaign Monitor: no MCP server or ChatGPT or Claude connector was found on campaignmonitor.com, and the official MCP Registry lists none from Campaign Monitor (checked 20 November 2026).

[ Source \[2\] · Official MCP Registry, search for "campaign", 20 Nov 2026: entries from other publishers ](#source-2)

04 · Webhooks

## Does Campaign Monitor have webhooks?

Lists

Campaign Monitor offers webhooks on a list for Subscribe, Update and Deactivate events, created and managed through the API. Its docs say: "Webhooks come in handy for keeping your subscribers in sync."

[ Source \[3\] · Campaign Monitor API v3.3: Webhooks ](#source-3)

05 · Zapier, Make, n8n

## Does Campaign Monitor work with Zapier, Make or n8n?

Zapier and Make

Campaign Monitor has a Zapier app with triggers and actions, such as "Add Subscriber: Create a new subscriber on a list." Make lists a Campaign Monitor app with modules such as Add a Subscriber and Watch Subscribers. No Campaign Monitor app was found on n8n on 20 November 2026; its page returns 404.

[ Source \[4\] · Zapier: Campaign Monitor integrations ](#source-4)

06 · Routes

## How can I connect Campaign Monitor to ChatGPT or Claude today?

A Campaign Monitor business has three routes today, and they do different jobs.

www.campaignmonitor.com Your Campaign Monitor business account

1. Route 1  
### The Campaign Monitor API and webhooks  
For developers, with an API key or OAuth.

  - Add and update subscribers: with code
  - Changes sent to other software: list webhooks
  - Ask in plain words: needs code
2. Route 2  
### The Campaign Monitor Zapier and Make apps  
Triggers and actions in Zaps and Make scenarios.

  - Add and update subscribers: Add Subscriber
  - Changes sent to other software: triggers
  - Ask in plain words: no
3. Route 3  
### [A cloud browser](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server.md)  
You sign in to your Campaign Monitor business account in a browser that runs in the cloud, and your AI agent works on the screens you use: campaigns, lists and subscribers, segments, reports. Cotlet, which publishes this page, is a cloud browser of this kind.

  - Add and update subscribers: with your login
  - Changes sent to other software: with your login
  - Ask in plain words: with your login

To connect your AI: [Campaign Monitor MCP server](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server.md).

07 · How Cotlet scores

## How Cotlet scores API & MCP access

Cotlet scores one thing: how easily a business can connect its own software or AI agent to its own account. Five checks give up to 10 points, and the points give the Cotlet API & MCP access score, from 1 to 5.

Points to score

Campaign Monitor · 7 points
1. 1 0 or 1
2. 2 2 to 4
3. 3 5 or 6
4. 4 7 or 8
5. 5 9 or 10

Where the 10 points come from

1. API 3 of 3
2. MCP 0 of 3
3. Zapier, Make, n8n 2 of 2
4. Webhooks 1 of 1
5. Data export 1 of 1

__How Cotlet scores API & MCP access: the five checks__
| Check | Points | What earns them |
| ------------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Official API for the business account | 0 to 3 | 3: public and self-serve, reads and writes. 2: public, but read only or on a higher plan. 1: by partner approval or as a paid add-on. 0: none |
| Official MCP server | 0 to 3 | 3: reads and writes the business account. 2: works on the business account, read only or limited. 1: exists, but not for the business account, such as an app in ChatGPT for clients. 0: none |
| Zapier, Make, n8n | 0 to 2 | 2: an app on two or more of them, with actions. 1: an app on one, or triggers only. 0: none |
| Webhooks | 0 or 1 | 1: documented webhooks for business events |
| Data export | 0 or 1 | 1: an official export, such as CSV, a report download or a data add-on |

__How Cotlet scores API & MCP access: points to score__
| Points | Score |
| ------- | ---------- |
| 9 or 10 | 5 out of 5 |
| 7 or 8 | 4 out of 5 |
| 5 or 6 | 3 out of 5 |
| 2 to 4 | 2 out of 5 |
| 0 or 1 | 1 out of 5 |

Every score rests on the sources listed on the page and carries the date it was checked. A score changes when the facts change. Cotlet sells a cloud browser that connects AI agents to web apps such as Campaign Monitor, and says so on every page of this catalog.

08 · Sources

## Sources

1. \[1\]  
[Campaign Monitor API v3.3: Getting started](https://www.campaignmonitor.com/api/v3-3/getting-started/)  
campaignmonitor.com Checked 20 Nov 2026
2. \[2\]  
[Official MCP Registry, search for "campaign", 20 Nov 2026: entries from other publishers](https://registry.modelcontextprotocol.io/v0/servers?search=campaign)  
registry.modelcontextprotocol.io Checked 20 Nov 2026
3. \[3\]  
[Campaign Monitor API v3.3: Webhooks](https://www.campaignmonitor.com/api/v3-3/webhooks/)  
campaignmonitor.com Checked 20 Nov 2026
4. \[4\]  
[Zapier: Campaign Monitor integrations](https://zapier.com/apps/campaign-monitor/integrations)  
zapier.com Checked 20 Nov 2026
5. \[5\]  
[Make: Campaign Monitor app and its modules; n8n.io/integrations/campaign-monitor returns 404, 20 Nov 2026](https://apps.make.com/campaign-monitor)  
apps.make.com, n8n.io Checked 20 Nov 2026
6. \[6\]  
[Campaign Monitor Help: Export subscribers](https://help.campaignmonitor.com/articles/Knowledge/export-subscribers)  
help.campaignmonitor.com Checked 20 Nov 2026

## Something changed at Campaign Monitor?

Write to contact@cotlet.dev and we recheck this page.

[Report an inaccuracy](mailto:contact@cotlet.dev?subject=Campaign%20Monitor%20API%20status) [Connect Campaign Monitor to your AI](https://cotlet.dev/integrations/campaign-monitor-api-mcp-server.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.
