[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)

# Constant Contact API and MCP server

> Constant Contact has a full public REST API, v3, for contacts, lists, email campaigns and reports, and an official MCP server in beta that is built for transactional email (checked 22 Oct 2026). The MCP server does not work the lists, campaigns and reports of your marketing account. For the API you register an app, and since July 2026 a new app stays private to the user who created it until Constant Contact support approves it.

Email marketing platform for small businesses: email campaigns, contact lists and segments, reports on every send, plus automations, events and social posts.

## What is the Constant Contact API?

Cotlet's Constant Contact API exposes 12 endpoints for your own Constant Contact account: list emails, get email report, list contacts of an email, list contact lists, list segments, list contacts, get contact, create list, add contacts to a list, remove contacts from a list, copy email and schedule or send an email. The list_emails endpoint returns emails in Channels > Emails with name, subject and status, filtered by status. Each endpoint takes simple JSON inputs like limit, cursor or email_id and works both as an operation of the constant_contact_read or constant_contact_write MCP tool for agents and as a REST call for scripts.

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

Constant Contact has a full public REST API, v3, for contacts, lists, email campaigns and reports, and an official MCP server in beta that is built for transactional email (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Constant Contact with 12 endpoints (7 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Constant Contact have an official API?

Constant Contact has a full public REST API, v3, for contacts, lists, email campaigns and reports, and an official MCP server in beta that is built for transactional email (checked 22 Oct 2026). The MCP server does not work the lists, campaigns and reports of your marketing account. For the API you register an app, and since July 2026 a new app stays private to the user who created it until Constant Contact support approves it.

| Task | Constant Contact official | Cotlet |
|---|---|---|
| List emails with their status | Yes: v3 API; you build the calls and paging yourself | Yes |
| Read opens, clicks, bounces and unsubscribes of a sent email | Yes: v3 reporting endpoints | Yes |
| List contacts who did not open, clicked, bounced or unsubscribed | Yes: v3 tracking reports, one email activity at a time | Yes |
| List lists, segments and contacts | Yes: v3 API | Yes |
| Add contacts to a list in bulk | Yes: v3 bulk activity, up to 500 contact IDs per call | Yes |
| Schedule or send an email to a list or segment | Yes: v3 API schedules an email campaign activity | Yes |
| Do all of the above from an AI agent over MCP | No: The official MCP server (beta) sends transactional email | Yes |

Sources: [Constant Contact for Agents (developer beta)](https://ctct.dev/), [Constant Contact V3 API release notes](https://developer.constantcontact.com/api_guide/index.html), [Constant Contact developers: Email reporting overview](https://developer.constantcontact.com/api_guide/email_reporting_overview.html), [Constant Contact developers: Contact lists overview](https://developer.constantcontact.com/api_guide/lists_overview.html)

## For AI agents

```text
Constant Contact has a full public REST API, v3, for contacts, lists, email campaigns and reports, and an official MCP server in beta that is built for transactional email (checked 22 Oct 2026). The MCP server does not work the lists, campaigns and reports of your marketing account. For the API you register an app, and since July 2026 a new app stays private to the user who created it until Constant Contact support approves it.
Cotlet provides a hosted MCP server and REST API for Constant Contact: 12 tools (7 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=constant-contact, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    constant_contact_read, constant_contact_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/constant-contact, each operation at its own route, e.g. POST /api/v1/constant-contact/emails/{email_id}
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_emails, get_email_report, list_email_contacts, list_lists, list_segments, list_contacts, get_contact, create_list, add_contacts_to_list, remove_contacts_from_list, copy_email, send_email
Confirm      add_contacts_to_list, send_email (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/constant-contact-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=constant-contact, requests Constant Contact in the Cotlet console and creates an API key there.
2. The user signs in to Constant Contact once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Constant Contact 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 Constant Contact 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 Constant Contact 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 Constant Contact 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 Constant Contact 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 Constant Contact 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 Constant Contact's terms; Cotlet is not affiliated with Constant Contact.
```

## What can an AI agent do in Constant Contact?

Cotlet is best for Constant Contact account owners and managers who want their AI agent to report on sends, build lists and schedule emails without running or fixing a server.

- **[Weekly email campaign report](https://cotlet.dev/integrations/constant-contact-api-mcp-server/weekly-email-report.md)** (runs: weekly): "Every Monday, report opens, clicks, bounces and unsubscribes for each Constant Contact email sent last week, name the weakest one and list how many contacts did not open it." → `list_emails`, `get_email_report`, `list_email_contacts`
- **[Build a re-engagement list from non-openers](https://cotlet.dev/integrations/constant-contact-api-mcp-server/re-engagement-list.md)**: "Find contacts who did not open any of my last 3 sent emails, put them in a new list called Re-engage Oct 2026 and tell me how many there are." → `list_emails`, `list_email_contacts`, `get_contact`, `list_lists`, `create_list`, `add_contacts_to_list`
- **[Schedule a recurring email](https://cotlet.dev/integrations/constant-contact-api-mcp-server/schedule-recurring-email.md)** (runs: weekly): "On the 1st of each month, copy last month's rent reminder email, tell me when the copy is ready for me to edit, then schedule it for the 3rd at 9:00 to the Tenants list." → `list_emails`, `copy_email`, `list_lists`, `send_email`
- **Add a segment's contacts to a list**: "Take everyone in the segment Webinar attendees and add them to the list Webinar follow-up, then tell me how many are in the list." → `list_segments`, `list_lists`, `list_contacts`, `add_contacts_to_list`
- **Find contacts who clicked a link**: "For my last sent email, list the contacts who clicked a link, with their lists and tags, so I can hand them to sales." → `list_emails`, `list_email_contacts`, `get_contact`

## Can Constant Contact automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Constant Contact 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 weekly email campaign report, 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/constant-contact/emails. | 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/constant-contact/emails with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 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 Constant Contact.

### list_emails

Emails in Channels > Emails with name, subject and status, filtered by status. Access: read. REST: `GET /api/v1/constant-contact/emails`. MCP: `constant_contact_read → list_emails`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | draft, scheduled or sent. Default: all. |
| `limit` | integer | no | How many items to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the emails of your account as Channels > Emails shows them, one page per call; pass next_cursor back as cursor for the next page. status filters like the Status drop-down: draft, scheduled or sent. A sent email has sent_at, a scheduled one has scheduled_for and the audience it will go to. Use email_id in the report, copy and send tools.

Example response:

```json
{
  "emails": [
    {
      "email_id": "3f6c1a52-8b7e-4d19-a0c4-5e2b9d7f1a63",
      "name": "October newsletter",
      "subject": "Five tips for your autumn menu",
      "status": "sent",
      "sent_at": "2026-10-14T09:00:00Z"
    },
    {
      "email_id": "7b1e9c30-4d2a-4f86-9a15-c3e8d0b72f41",
      "name": "Rent reminder, October",
      "subject": "Rent is due on Nov 5",
      "status": "scheduled",
      "scheduled_for": "2026-11-03T08:00:00Z",
      "audience": "Tenants"
    }
  ],
  "next_cursor": null
}
```

### get_email_report

Sends, bounces, opens, clicks, unsubscribes and did-not-open of one sent email, with its rates. Access: read. REST: `GET /api/v1/constant-contact/emails/{email_id}/report`. MCP: `constant_contact_read → get_email_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `email_id` | string | yes | Email ID from list_emails. |

Returns the figures of the email's Reporting page. Opens and clicks are unique counts; proxy opens are reported apart and left out of the open rate. open_rate is unique opens divided by sends minus bounces; click_rate uses unique clicks the same way. A draft or scheduled email has no report and returns an error.

Example response:

```json
{
  "email_id": "3f6c1a52-8b7e-4d19-a0c4-5e2b9d7f1a63",
  "name": "October newsletter",
  "sent_at": "2026-10-14T09:00:00Z",
  "sends": 1204,
  "bounces": 17,
  "delivered": 1187,
  "unique_opens": 412,
  "unique_clicks": 96,
  "unsubscribes": 5,
  "spam_reports": 0,
  "did_not_open": 775,
  "open_rate": 34.7,
  "click_rate": 8.1
}
```

### list_email_contacts

Contacts who did not open, opened, clicked, bounced or unsubscribed from one sent email. Access: read. REST: `GET /api/v1/constant-contact/email-contacts`. MCP: `constant_contact_read → list_email_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `email_id` | string | yes | Email ID from list_emails. |
| `type` | enum | yes | did_not_open, opened, clicked, bounced or unsubscribed. |
| `limit` | integer | no | How many items to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the contacts behind a number on the email's Reporting page, one page per call; pass next_cursor back as cursor for the next page. type picks the list: did_not_open (sent the email, never opened it), opened, clicked, bounced or unsubscribed. Each row has the contact_id to use in get_contact and add_contacts_to_list.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "c1a2b3d4-0001-4e5f-8a9b-1c2d3e4f5a01",
      "email": "lena.ortiz@example.com",
      "name": "Lena Ortiz"
    },
    {
      "contact_id": "c1a2b3d4-0002-4e5f-8a9b-1c2d3e4f5a02",
      "email": "sam.okafor@example.com",
      "name": "Sam Okafor"
    }
  ],
  "next_cursor": "eyJwIjoyfQ"
}
```

### list_lists

Your contact lists with name and number of contacts. Access: read. REST: `GET /api/v1/constant-contact/lists`. MCP: `constant_contact_read → list_lists`.

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

Returns the lists on the Contacts > Lists page, one page per call. An account holds up to 1,000 lists. Use list_id in list_contacts, add_contacts_to_list, remove_contacts_from_list and send_email.

Example response:

```json
{
  "lists": [
    {
      "list_id": "5a8d3f21-6b9c-4e07-8d14-2f7c9e0a1b36",
      "name": "Tenants",
      "contacts": 312
    },
    {
      "list_id": "9d2e4b7a-1c3f-4a58-b6e0-7f8a2c5d1e90",
      "name": "Re-engage Oct 2026",
      "contacts": 0
    }
  ],
  "next_cursor": null
}
```

### list_segments

Your saved segments with name. Account Owners and Account Managers only. Access: read. REST: `GET /api/v1/constant-contact/segments`. MCP: `constant_contact_read → list_segments`.

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

Returns the segments of Contacts > Segments, one page per call. A segment picks contacts by criteria such as email activity, contact details, list membership or tags, and is evaluated again when an email sends. Use segment_id in list_contacts, add_contacts_to_list and send_email.

Example response:

```json
{
  "segments": [
    {
      "segment_id": 4417,
      "name": "Webinar attendees"
    },
    {
      "segment_id": 4420,
      "name": "Opened in the last 90 days"
    }
  ],
  "next_cursor": null
}
```

### list_contacts

Contacts of the account, of one list or of one segment, with email, name and permission to send. Access: read. REST: `GET /api/v1/constant-contact/contacts`. MCP: `constant_contact_read → list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list_id` | string | no | Only contacts of this list. |
| `segment_id` | integer | no | Only contacts of this segment. Do not combine with list_id. |
| `search` | string | no | Part of an email address or name. |
| `limit` | integer | no | How many items to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns contacts one page per call; pass next_cursor back as cursor for the next page. Give list_id or segment_id to narrow it, not both. permission_to_send shows whether the contact can be mailed, with unsubscribed for contacts who opted out. Use contact_id in get_contact and add_contacts_to_list.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "c1a2b3d4-0001-4e5f-8a9b-1c2d3e4f5a01",
      "email": "lena.ortiz@example.com",
      "first_name": "Lena",
      "last_name": "Ortiz",
      "permission_to_send": "implicit"
    },
    {
      "contact_id": "c1a2b3d4-0004-4e5f-8a9b-1c2d3e4f5a04",
      "email": "tom.becker@example.com",
      "first_name": "Tom",
      "last_name": "Becker",
      "permission_to_send": "unsubscribed"
    }
  ],
  "next_cursor": "eyJwIjoyfQ"
}
```

### get_contact

One contact with email, name, permission to send, lists and tags. Access: read. REST: `GET /api/v1/constant-contact/contacts/{contact_id}`. MCP: `constant_contact_read → get_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts or list_email_contacts. |

Returns the contact as its page in Contacts shows it, with the names of the lists it belongs to and its tags. Use it to check permission_to_send and list membership before you add or mail someone. A contact belongs to at most 50 lists.

Example response:

```json
{
  "contact_id": "c1a2b3d4-0001-4e5f-8a9b-1c2d3e4f5a01",
  "email": "lena.ortiz@example.com",
  "first_name": "Lena",
  "last_name": "Ortiz",
  "permission_to_send": "implicit",
  "lists": [
    "Tenants",
    "Newsletter"
  ],
  "tags": [
    "2026 renewal"
  ]
}
```

### create_list

Create an empty contact list with a unique name. Access: write. REST: `POST /api/v1/constant-contact/lists`. MCP: `constant_contact_write → create_list`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | List name, unique in the account. |
| `description` | string | no | Up to 255 characters. |

Creates a list that no email goes to until you schedule one to it, and returns its list_id. The name must differ from every other list; a repeated name fails. It reaches no one and a list you do not need is simply left empty, so it does not wait for your OK.

Example response:

```json
{
  "list_id": "9d2e4b7a-1c3f-4a58-b6e0-7f8a2c5d1e90",
  "name": "Re-engage Oct 2026",
  "contacts": 0
}
```

### add_contacts_to_list

Add up to 500 contacts, or a whole segment, to a list. Access: write, asks the user first. REST: `POST /api/v1/constant-contact/lists/{list_id}/contacts-to-lists`. MCP: `constant_contact_write → add_contacts_to_list`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list_id` | string | yes | List ID from list_lists or create_list. |
| `contact_ids` | array | no | Up to 500 contact IDs. Use this or segment_id. |
| `segment_id` | integer | no | Add every contact of this segment. Use this or contact_ids. |

Adds contacts to a list in one call. Give contact_ids (up to 500) or segment_id, not both. The contacts then receive any email scheduled to that list, and a large add can move your account into a higher contact tier. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "list_id": "9d2e4b7a-1c3f-4a58-b6e0-7f8a2c5d1e90",
  "requested": 3,
  "added": 3
}
```

### remove_contacts_from_list

Take contacts off a list; they stay in your account. Access: write. REST: `DELETE /api/v1/constant-contact/lists/{list_id}/contacts-from-lists`. MCP: `constant_contact_write → remove_contacts_from_list`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list_id` | string | yes | List ID from list_lists or create_list. |
| `contact_ids` | array | yes | Contact IDs to take off the list. |

Removes the contacts from this one list, as Actions > Remove from list does in Contacts. They are not deleted and stay on every other list. It reaches no one and add_contacts_to_list undoes it in one call, so it does not wait for your OK.

Example response:

```json
{
  "list_id": "5a8d3f21-6b9c-4e07-8d14-2f7c9e0a1b36",
  "removed": 2
}
```

### copy_email

Make a draft copy of an existing email. Access: write. REST: `POST /api/v1/constant-contact/emails/{email_id}/copy`. MCP: `constant_contact_write → copy_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `email_id` | string | yes | Email ID of the email to copy, draft, scheduled or sent. |
| `name` | string | no | Name of the copy. |

Creates a draft with the same content as the source email, the way Copy on the email's Details tab does, and returns its email_id. It does not edit text or links, and it sends nothing. It reaches no one and the draft can be left unused, so it does not wait for your OK.

Example response:

```json
{
  "email_id": "7b1e9c30-4d2a-4f86-9a15-c3e8d0b72f41",
  "name": "Rent reminder, October",
  "status": "draft"
}
```

### send_email

Send a draft now or schedule it up to a year ahead, to lists or one segment. Access: write, asks the user first. REST: `POST /api/v1/constant-contact/emails/{email_id}`. MCP: `constant_contact_write → send_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `email_id` | string | yes | Email ID from list_emails. |
| `list_ids` | array | no | IDs of the lists to send to. Use this or segment_id. |
| `segment_id` | integer | no | Send to this segment. Use this or list_ids. |
| `send_at` | datetime | no | ISO 8601 date and time with offset. Leave out to send now. |
| `resend_to_non_openers` | boolean | no | Also resend to contacts who did not open it. Default: false. |

Sets the audience and the time of an email, like the Schedule page. Give list_ids or one segment_id; leave send_at out to send now. send_at is a date and time with an offset, in the future and within a year. Sending needs an Account Owner or Account Manager login, and can take up to 30 minutes on a large list. resend_to_non_openers is not available with a subject line A/B test and on some plans. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "email_id": "7b1e9c30-4d2a-4f86-9a15-c3e8d0b72f41",
  "status": "scheduled",
  "scheduled_for": "2026-11-03T08:00:00Z",
  "audience": "Tenants"
}
```

## How do I connect Constant Contact to Claude Code, Codex or Cursor?

Connecting Constant Contact takes three steps: sign up, sign in to Constant Contact 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 Constant Contact to your agent.

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

2. **Sign in to Constant Contact in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Constant Contact 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 Constant Contact 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.

```
Every Monday, report opens, clicks, bounces and unsubscribes for each Constant Contact email sent last week, name the weakest one and list how many contacts did not open it.
```

### Call Constant Contact 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/constant-contact 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/constant-contact/emails/7b1e9c30-4d2a-4f86-9a15-c3e8d0b72f41 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"list_ids":["5a8d3f21-6b9c-4e07-8d14-2f7c9e0a1b36"],"send_at":"2026-11-03T09:00:00+01:00"}'
```

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

```
{
  "email_id": "7b1e9c30-4d2a-4f86-9a15-c3e8d0b72f41",
  "status": "scheduled",
  "scheduled_for": "2026-11-03T08:00:00Z",
  "audience": "Tenants"
}
```

## Why use Cotlet for Constant Contact?

**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 Constant Contact 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 Constant Contact changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Constant Contact to Cotlet?

Yes. You sign in to Constant Contact yourself, in your own Cloud Browser, and we never save your password. Your agents only get Constant Contact 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 Constant Contact integration?**

No, Cotlet is independent of Constant Contact. Constant Contact's own API is too limited for this work. Cotlet works through your own Constant Contact account, the way you use Constant Contact 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 Constant Contact in your console: your agents lose access at once and you stay signed in. Signing out of Constant Contact in the browser works too, and Reset browser deletes the whole profile.

## Is there a Constant Contact MCP server on GitHub?

Yes. Community MCP servers exist on GitHub that wrap the v3 API, usually maintained by one person. You install one on your own computer, register your own Constant Contact app for it, and keep it running yourself; when the API or the app changes, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, register your own Constant Contact app, authorize it, add it to each MCP client | Sign up, sign in to Constant Contact once, add one MCP server or API key |
| When Constant Contact 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 Constant Contact access | Tokens of your own app in a file on your computer, readable by any program you run | In your own Cloud Browser in the EU, session encrypted, only for the apps you enable, disabled for agents in one click |
| When the access expires | Tools fail until you authorize the app again by hand | Your Cloud Browser keeps you signed in; if Constant Contact 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 Constant Contact 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 Constant Contact API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Constant Contact 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 Constant Contact 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 Constant Contact 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 Constant Contact only after you enable it. When Constant Contact 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 Constant Contact, sign out of Constant Contact 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.
- **Constant Contact's terms:** You use your own Constant Contact account and stay responsible for following Constant Contact's terms. Cotlet is independent and not affiliated with Constant Contact. [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 Constant Contact in the console and press Request access. Then you create your API key and connect Constant Contact there.

**Do I need to be technical?**

No. You sign in to Constant Contact 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 Constant Contact to Cotlet?**

Yes. You sign in to Constant Contact yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Constant Contact 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 Constant Contact 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 Constant Contact 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 Constant Contact's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Constant Contact 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 Constant Contact 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?**

Constant Contact 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 Constant Contact role does my agent need?**

An Account Owner or Account Manager login. Both can manage lists and contacts, view reports and send emails; a Campaign Creator can build emails but cannot send them or work with contacts. Segments are also for Owners and Managers (checked 22 Oct 2026).

**Does this replace the official Constant Contact for Agents MCP server?**

No, they do different jobs. The official beta is a developer API and MCP server for sending transactional email from your own code. Cotlet works the marketing account you already use: its lists, contacts, campaign reports and scheduled sends.

**Can my agent post or send messages in Constant Contact without asking me?**

No. Every call to add_contacts_to_list or send_email 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_list, remove_contacts_from_list, copy_email runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Constant Contact 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/constant-contact 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.