# Campaign Monitor MCP connector

Connect Campaign Monitor to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can look up and update your client accounts, lists, segments, admins and suppression lists, each person inside their own access, every call logged.

Source: https://elaichi.ai/connectors/campaignmonitor/

## Facts

| | |
| --- | --- |
| Application | Campaign Monitor |
| Category | Marketing Automation |
| AI tools | 117 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Campaign Monitor is connected

- Which Campaign Monitor clients are on monthly billing?
- Show me every list and segment for the Acme client
- Add jane@example.com to the Acme suppression list

## Connect Campaign Monitor in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Campaign Monitor.
2. Optionally set Share with, then press Connect.
3. Paste a Campaign Monitor API key. One person generates a token in Campaign Monitor and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Campaign Monitor tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Campaign Monitor MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Campaign Monitor MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Campaign Monitor MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Campaign Monitor MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Campaign Monitor MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Campaign Monitor to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Campaign Monitor tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Campaign Monitor through Elaichi

### Find the right list before a send

Marketing. Ask which lists and segments a client has before you plan a send, and get the names back without opening Campaign Monitor.

### Set up a new client account

Account management. Create the client account in Campaign Monitor, fill in its basics and set the primary contact, all from one conversation.

### Switch a client between billing plans

Finance. Move a client from pay as you go to monthly billing, or back again, and pull billing details across every client in one ask.

### Suppress an address the moment someone asks

Compliance. When an unsubscribe request or complaint comes in, add the address to the client's suppression list and confirm it is there.

### See which lists an email is on

Support. When a subscriber writes in, ask which of a client's lists their address belongs to and answer them straight away.

### Keep account admins current

IT. Add a new admin, update a name or email, or remove someone who has moved on, and check the admin list whenever you need.

## Elaichi vs Zapier MCP vs Composio for Campaign Monitor

All three can connect Campaign Monitor to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Campaign Monitor tools | Allow or restrict single Campaign Monitor tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Campaign Monitor call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Campaign Monitor to Claude?

Connect Campaign Monitor in Elaichi, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Campaign Monitor connects with an API key, so the sign-in step is pasting the key from your Campaign Monitor account settings. There is no OAuth application to register and no client ID or secret to generate.

### Does Campaign Monitor work with ChatGPT and Cursor as well as Claude?

Yes. Once Campaign Monitor is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Campaign Monitor once and every client sees it.

### What can an AI agent actually do with my Campaign Monitor data?

An agent can list your Campaign Monitor clients, create a new one, update its details and billing plan, and set its primary contact. It can show the lists and segments each client has, tell you which lists an email address is on, add an address to a suppression list, and add, update or remove admins on your account. Short, concrete asks such as which lists is this address on work better than long sentences.

### Does connecting Campaign Monitor give the AI every client and list in my account?

No. Access follows the Campaign Monitor account that was connected and the person who signed in to Elaichi, so an agent only reaches the clients, lists and admins that person is allowed to reach. Elaichi can narrow that further with roles and restrictions, and it never widens it.

### Can my team share one Campaign Monitor connection?

Yes. One person connects Campaign Monitor with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in as themselves, so the audit log names the person who made each change to a client, list or suppression list.

### Can I stop an agent from deleting or changing things in Campaign Monitor?

Yes. In Elaichi you can restrict any Campaign Monitor action, such as deleting a client or removing an admin, for a role or for one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Campaign Monitor connection when someone leaves?

Offboarding that person in Elaichi ends their access to Campaign Monitor at once, across every client they used. A shared Campaign Monitor connection keeps working for everyone else on the team. If you disconnect Campaign Monitor in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

### Does the Campaign Monitor MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Campaign Monitor is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Campaign Monitor?

Yes. Both let Claude, ChatGPT or Cursor use Campaign Monitor. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Campaign Monitor call.

### How is Elaichi different from Composio for Campaign Monitor?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Campaign Monitor: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 117 Campaign Monitor tools

Every tool below is callable through https://api.elaichi.ai/mcp once Campaign Monitor is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Campaign Monitor clients** (List). List all Campaign Monitor clients in your account. Returns an array of clients, each with ClientID and Name. Not paginated: all clients are returned in one response.

- **Create a Campaign Monitor client** (Create). Create a new Campaign Monitor client with basic contact information and no application access. Returns the new client's ClientID. Required: CompanyName, Country, TimeZone. Max 5 clients per 30 minutes.
- **Get single Campaign Monitor client by ID** (Get). Get the complete details for a Campaign Monitor client by id. Returns the client object including ApiKey, BasicDetails (ClientID, CompanyName, Country, TimeZone, and primary contact fields when a single person exists), and BillingDetails. Required: id.
- **Campaign Monitor clients update payg billing** (Update). Update PAYG billing settings for a Campaign Monitor client (currency, markups, and whether the client pays). Returns an empty 200 response on success. Required: client_id, Currency, CanPurchaseCredits, ClientPays, MarkupPercentage.
- **Campaign Monitor clients update monthly billing** (Update). Set monthly billing options for a Campaign Monitor client including currency, client payment, mark-up percentage, and monthly scheme. Returns an empty 200 response on success. Requires client_id, Currency, ClientPays, and MarkupPercentage. Supported currencies: USD, GBP, EUR, CAD, AUD, NZD.
- **Delete a Campaign Monitor client by ID** (Delete). Delete a Campaign Monitor client by id. Returns an empty 200 response on success.
- **Campaign Monitor clients update basics** (Update). Update the basic details (name, country, timezone) for a Campaign Monitor client. Returns an empty 200 response on success. Required: client_id, CompanyName, Country, TimeZone.
- **List all Campaign Monitor billing details** (List). Get billing details for your Campaign Monitor account. Returns a single object (not a list) with Credits, the number of credits in your account. Not paginated.

- **List all Campaign Monitor countries** (List). List the valid countries accepted by Campaign Monitor as input, typically when creating a client. Returns an array of country name strings (e.g. Afghanistan, Albania, Algeria, American Samoa).
- **List all Campaign Monitor timezones** (List). List valid timezones in Campaign Monitor accepted when creating a client. Returns a list of timezone display names such as '(GMT) Casablanca' or '(GMT) Dublin, Edinburgh, Lisbon, London'.
- **Campaign Monitor system date get current date** (Get). Get the current date and time in your Campaign Monitor account's timezone. Returns: SystemDate. The server's clock, useful for syncing lists or campaigns with an external system and accurately determining Campaign Monitor's server time when synchronizing.
- **Create a Campaign Monitor admin** (Create). Add an administrator to the account. Required: EmailAddress, Name. Returns {EmailAddress}.
- **List all Campaign Monitor admins** (List). List all administrators (active or invited) on the Campaign Monitor account. Returns an array with EmailAddress, Name and Status (Active or Waiting to Accept the Invitation) for each administrator. Not paginated.

- **Update a Campaign Monitor admin by ID** (Update). Update an administrator, identified by their current email address as id. Put the new address in EmailAddress to change it. Required: id (current email), EmailAddress, Name. Returns {EmailAddress}.
- **Delete a Campaign Monitor admin by ID** (Delete). Delete an administrator, identified by their email address as id. Required: id (email).
- **Get single Campaign Monitor admin by ID** (Get). Get the details of a single administrator on the Campaign Monitor account, identified by their email address as id. Returns EmailAddress, Name and Status (Active or Waiting to Accept the Invitation). Required: id (the administrator email address).

- **Campaign Monitor primary contact set** (Set). Set the primary contact for the account to an existing administrator. Required: email (query). Returns {EmailAddress}.
- **List all Campaign Monitor primary contact** (List). Get the primary contact for the Campaign Monitor account. Returns a single object (not a list) with the EmailAddress of the administrator selected as the account's primary contact. Not paginated.

- **Create a Campaign Monitor external session** (Create). Create an embedded session in Campaign Monitor that initiates a login session for a member of a client. Returns a single-use SessionUrl that starts the session (typically loaded in an iframe). Required: Email, Chrome, Url, IntegratorID, ClientID. Chrome only accepts All, Tabs, or None.
- **List all Campaign Monitor client lists** (List). List all subscriber lists belonging to a Campaign Monitor client. Returns an array of lists, each with ListID and Name. Not paginated. Required: client_id.

- **Campaign Monitor client lists lists for email** (Action). List all subscriber lists across a Campaign Monitor client to which an email address is subscribed. Returns ListID, ListName, SubscriberState and DateSubscriberAdded (in the client's timezone) for each list. Required: client_id, email.

- **List all Campaign Monitor client segments** (List). List the segment definitions belonging to a Campaign Monitor client across all of their subscriber lists. Returns an array of segments, each with ListID, SegmentID, and Title. Required: client_id.
- **List all Campaign Monitor suppression list** (List). List suppression entries for a Campaign Monitor client. Required: client_id.
- **Campaign Monitor suppression list suppress** (List). Add email addresses to a Campaign Monitor client's suppression list. Returns an empty 200 response on success. Required: client_id and EmailAddresses.
- **Campaign Monitor suppression list unsuppress** (List). Remove an email address from a Campaign Monitor client's suppression list. Returns an empty 200 response on success. Required: client_id and email.
- **List all Campaign Monitor client templates** (List). List templates belonging to a Campaign Monitor client. Returns an array of templates, each with TemplateID, Name, PreviewURL and ScreenshotURL. Not paginated. Required: client_id.

- **Campaign Monitor credits transfer** (Action). Transfer credits between your account and a client in Campaign Monitor. Returns the resulting AccountCredits and ClientCredits balances. Required: client_id, Credits, CanUseMyCreditsWhenTheyRunOut.
- **Create a Campaign Monitor person** (Create). Add a person to a client. Required: client_id, EmailAddress, Name, AccessLevel. Password is optional (min 6 characters if supplied). Returns {EmailAddress}.
- **List all Campaign Monitor people** (List). List all people (active or invited) associated with a Campaign Monitor client. Account administrators are excluded. Returns the EmailAddress, Name, AccessLevel, and Status of each person. Required: client_id.
- **Update a Campaign Monitor person by ID** (Update). Update a person in a client, identified by their current email address as id. Put the new address in EmailAddress to change it. Required: id (current email), client_id, EmailAddress, Name, AccessLevel.
- **Delete a Campaign Monitor person by ID** (Delete). Delete a person from a client, identified by their email address as id. Required: id (email), client_id.
- **Get single Campaign Monitor person by ID** (Get). Get the details of a single person associated with a Campaign Monitor client, identified by their email address as id. Returns EmailAddress, Name, AccessLevel and Status. Required: id (the person email address), client_id.

- **List all Campaign Monitor tags** (List). List campaign tags for a Campaign Monitor client in ascending order. Returns an array with Name and NumberOfCampaigns for each tag. Not paginated. Required: client_id.

- **Campaign Monitor campaigns list sent** (List). List Campaign Monitor campaigns for a client that have already been sent, most recent first by default. The response is a paged wrapper: Results (each with CampaignID, Name, Subject, FromName, FromEmail, ReplyTo, SentDate, TotalRecipients, WebVersionURL, WebVersionTextURL, Tags), ResultsOrderedBy, OrderDirection, PageNumber, PageSize, RecordsOnThisPage, TotalNumberOfRecords, NumberOfPages. Use page and pagesize (10-1000, default 1000) to walk through pages, and optionally filter with sentFromDate, sentToDate and tags or sort with orderdirection. Required: client_id.

- **Campaign Monitor campaigns list scheduled** (List). List Campaign Monitor campaigns for a client that are scheduled to send in the future. Returns scheduled campaigns with CampaignID, Name, Subject, FromName, FromEmail, ReplyTo, DateScheduled, ScheduledTimeZone, DateCreated, PreviewURL, PreviewTextURL, and Tags. Required: client_id.
- **Campaign Monitor campaigns list drafts** (List). List Campaign Monitor draft campaigns for a client that have been created but not yet scheduled or sent. Returns drafts with CampaignID, Name, Subject, FromName, FromEmail, ReplyTo, DateCreated, PreviewURL, PreviewTextURL, and Tags. Required: client_id.
- **Create a Campaign Monitor campaign** (Create). Create (but do not send) a draft Campaign Monitor campaign from HTML content hosted at a URL. Returns the new campaign ID as a JSON string (201 Created). Required: client_id, Name, Subject, FromName, FromEmail, ReplyTo, HtmlUrl, and at least one of ListIDs or SegmentIDs (if you use SegmentIDs, omit ListIDs). TextUrl is optional; if omitted the text version is generated from the HTML. InlineCss defaults to true.

- **Campaign Monitor campaigns create from template** (Create). Create a draft Campaign Monitor campaign from a saved template. Required: client_id, Name, Subject, FromName, FromEmail, ReplyTo, TemplateID, ListIDs or SegmentIDs. TemplateContent supplies Singlelines, Multilines, Images and Repeaters (Items with optional Layout), matched to the template's tags in the order they appear. Returns the new campaign ID as a JSON string. Email builder templates are not supported.

- **Campaign Monitor campaigns send** (Send). Schedule a draft campaign in Campaign Monitor for immediate or future delivery. Returns an empty 200 response on success. Required: campaign_id, ConfirmationEmail, SendDate.
- **Campaign Monitor campaigns send preview** (Send). Send a preview of a draft campaign in Campaign Monitor to a list of test email addresses; personalization tags are populated using fallback values. Returns an empty 200 response on success. Required: campaign_id, PreviewRecipients.
- **Campaign Monitor campaigns email client usage** (Action). List the email clients Campaign Monitor subscribers used to open a campaign. Returns a list of entries with: Client, Version, Percentage, Subscribers. Required: campaign_id.
- **Campaign Monitor campaigns lists and segments** (Action). Get the lists and segments a Campaign Monitor campaign was sent to. Returns two collections: Lists (each with ListID and Name) and Segments (each with ListID, SegmentID, and Title). Required: campaign_id.
- **Campaign Monitor campaigns recipients** (Action). List every subscriber a Campaign Monitor campaign was sent to, with the list they belong to. Returns paged results: Results (with EmailAddress and ListID), ResultsOrderedBy, OrderDirection, PageNumber, PageSize, RecordsOnThisPage, TotalNumberOfRecords, NumberOfPages. Required: campaign_id.
- **Campaign Monitor campaigns bounces** (Action). List email bounces received by a Campaign Monitor campaign. Returns a paged result with subscriber email, list id, bounce type (Hard/Soft), date, and bounce reason. Required: campaign_id.
- **Campaign Monitor campaigns opens** (Action). List subscribers who opened a Campaign Monitor campaign. Returns a paged result with email address, list id, date, IP address, and geocoded location (latitude, longitude, city, region, country code, country name). Required: campaign_id.
- **Campaign Monitor campaigns clicks** (Action). List subscribers who clicked a link in a Campaign Monitor campaign. Returns a paged result with email address, link URL, list id, date, IP address, and geocoded location. Required: campaign_id.
- **Campaign Monitor campaigns unsubscribes** (Action). List subscribers who unsubscribed via a Campaign Monitor campaign. Returns a paged result with email address, list id, date, and the IP address they unsubscribed from. Required: campaign_id.
- **Campaign Monitor campaigns spam complaints** (Action). List subscribers who marked a Campaign Monitor campaign as spam. Returns a paged result with email address, list id, and the date they marked the campaign as spam. Required: campaign_id.
- **Campaign Monitor campaigns unschedule** (Action). Cancel a scheduled Campaign Monitor campaign and move it back into drafts. Returns an empty 200 response on success. Required: campaign_id.
- **Campaign Monitor campaigns summary** (Action). Get a basic summary of results for a sent Campaign Monitor campaign. Returns: Name, Recipients, TotalOpened, UniqueOpened, Clicks, Unsubscribed, Bounced, SpamComplaints, Forwards, Likes, Mentions, WebVersionURL, WebVersionTextURL, WorldviewURL. Required: campaign_id.
- ...and 67 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
