# Constant Contact MCP connector

The Constant Contact connector brings your contacts, contact lists, tags, users and account activity into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person works inside their own Constant Contact access with every action logged.

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

## Facts

| | |
| --- | --- |
| Application | Constant Contact |
| Category | Marketing Automation |
| AI tools | 131 |
| Authentication | Connects over OAuth |
| 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 Constant Contact is connected

- Add Priya Shah to the Spring webinar list and tag her VIP
- Which contact lists grew the most this month?
- Show me contacts tagged Trade show that are not on any list

## Connect Constant Contact in Elaichi

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

1. Open Connections, choose Add connection, and pick Constant Contact.
2. Optionally set Share with, then press Connect.
3. Approve it in Constant Contact. Constant Contact's own window opens. Whoever approves it decides what this connection can reach.

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

## Constant Contact 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.

## Constant Contact 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`.

## Constant Contact 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.

## Constant Contact 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.

## Constant Contact 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 Constant Contact 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 Constant Contact 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 Constant Contact through Elaichi

### Build the list for the next send

Marketing. Ask for every contact tagged Webinar attendee who is not yet on the Autumn newsletter list, then have them added in one go. The list is ready before you open Constant Contact.

### Add a new lead after the call

Sales. Say who you just spoke to, their email and what they care about. The contact is created, tagged and placed on the right list without leaving the conversation.

### Tag everyone who showed up

Events. Paste the attendee sheet and have each person matched to their Constant Contact record, updated if they exist and created if they do not, with the event tag applied.

### Fix a contact before the newsletter goes

Customer success. A customer changed roles or company. Ask for their record, update the name, email or tags, and move them off lists that no longer fit.

### See what the account did last week

Marketing. Ask what activities ran in Constant Contact over the past seven days and get a plain summary of imports, list changes and updates, with who did what.

### Set up a new teammate's seat

Operations. When someone joins the marketing team, ask for a Constant Contact user to be created and check the account summary and company logos are current for their region.

## Elaichi vs Zapier MCP vs Composio for Constant Contact

All three can connect Constant Contact 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 Constant Contact tools | Allow or restrict single Constant Contact 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 Constant Contact 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 Constant Contact to Claude?

Open Elaichi, choose Constant Contact and sign in with your normal Constant Contact login over OAuth. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Constant Contact is now available in Claude as you.

### Does Constant Contact work with ChatGPT and Cursor as well as Claude?

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

### What can an AI agent actually do with my Constant Contact data?

An agent can look up, create, update and remove Constant Contact contacts, contact lists and tags, add users, review account activity and update account summaries and company logos. In practice that means adding a lead after a call, building a list from a tag or cleaning up a record before a send. Short, specific asks such as add this person to the Spring list work better than long paragraphs.

### Does connecting Constant Contact give the AI access to all my lists and contacts?

No. An agent working through Constant Contact in Elaichi sees exactly what the person who signed in can see, nothing more. Elaichi can narrow that access further with roles and restrictions, but it can never widen it beyond what Constant Contact already grants that person.

### Can my team share one Constant Contact connection?

Yes. One person connects Constant Contact in Elaichi and shares it with a team, and nobody else ever handles the Constant Contact login. Each teammate still signs in to Elaichi as themselves, so the audit log records who added, changed or removed each contact or list.

### Can I stop an agent from deleting or changing things in Constant Contact?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Constant Contact contacts while restricting deleting contacts or lists, set on a role or on 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 Constant Contact connection when someone leaves?

Offboarding a person in Elaichi ends their Constant Contact access through every client at once. A shared Constant Contact connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Constant Contact once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

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

Yes. Constant Contact 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 Constant Contact?

Yes. Both let Claude, ChatGPT or Cursor use Constant Contact. 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 Constant Contact call.

### How is Elaichi different from Composio for Constant Contact?

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 Constant Contact: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 131 Constant Contact tools

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

- **List all Constant Contact contacts** (List). List Constant Contact contacts. Returns each contact's contact_id, email_address, first_name, last_name, created_at, list_memberships, and notes; use the include query parameter to add sub-resources such as custom_fields, taggings, phone_numbers, street_addresses, and sms_channel.
- **Get single Constant Contact contact by ID** (Get). Get a single Constant Contact contact by id (the contact's contact_id UUID). Returns: contact_id, email_address, first_name, last_name, job_title, company_name, birthday_month, birthday_day, anniversary, created_at, updated_at, custom_fields, phone_numbers, street_addresses, list_memberships, notes, sms_channel, and 4 more. Required: id.
- **Create a Constant Contact contact** (Create). Create a new Constant Contact contact. Returns the created contact including contact_id, email_address, first_name, last_name, and list_memberships. Required: email_address, create_source. Up to 25 notes per contact.
- **Update a Constant Contact contact by ID** (Update). Update an existing Constant Contact contact by id (full replace: omitted fields such as list_memberships or phone_numbers are cleared). Returns the updated contact. Required: id, email_address, update_source.
- **Delete a Constant Contact contact by ID** (Delete). Delete a Constant Contact contact by id. Returns an empty 204 response on success. Required: id.
- **Constant Contact contacts upsert** (Upsert). Create or update a Constant Contact contact from sign-up form data without first checking whether the contact already exists. Returns: contact_id, action. Requires email_address with list_memberships, or sms_channel for SMS-only contacts. Only use when the contact gave explicit permission to be emailed, such as via a sign-up form.
- **List all Constant Contact contact lists** (List). List all Constant Contact contact lists. Returns each list's list_id, name, description, favorite, created_at, updated_at, deleted_at, and membership_count.
- **Get single Constant Contact contact list by ID** (Get). Get details about a specific Constant Contact contact list by id (list_id). Returns: list_id, name, description, favorite, created_at, updated_at, deleted_at. Required: id.
- **Create a Constant Contact contact list** (Create). Create a new Constant Contact contact list. Returns the created list including list_id, name, description, favorite, created_at, and updated_at. Requires name (max 255 characters) and favorite.
- **Update a Constant Contact contact list by ID** (Update). Update an existing Constant Contact contact list specified by id (list_id). Returns the updated list including list_id, name, description, favorite, created_at, and updated_at. Requires name and favorite.
- **Delete a Constant Contact contact list by ID** (Delete). Delete a Constant Contact contact list by id. The delete runs as an asynchronous activity — Returns: activity_id, state, created_at, updated_at, percent_done, activity_errors, _links. Required: id.
- **List all Constant Contact contact tags** (List). List all contact tags in the Constant Contact account. Returns each tag with: tag_id, name, contacts_count, created_at, updated_at, and tag_source.
- **Get single Constant Contact contact tag by ID** (Get). Get details for a single contact tag by id. Returns: tag_id, name, contacts_count, created_at, updated_at, tag_source. Required: id (tag_id).
- **Create a Constant Contact contact tag** (Create). Create a new contact tag in Constant Contact with a unique name. Returns the created tag with: tag_id, name, contacts_count, created_at, updated_at, and tag_source. Required: name.
- **Update a Constant Contact contact tag by ID** (Update). Rename an existing contact tag by id. Returns the updated tag with: tag_id, name, contacts_count, created_at, updated_at, and tag_source. Required: id, name. Tag name max length is 255 characters.
- **Delete a Constant Contact contact tag by ID** (Delete). Delete a contact tag by id; asynchronously un-assigns the tag from all contacts and then deletes it. Returns: activity_id, state, created_at, updated_at, percent_done, activity_errors, _links. Required: id.
- **List all Constant Contact users** (List). List the email addresses on your Constant Contact account. Returns each address's email_address, email_id, confirm_status, confirm_time, confirm_source_type, roles, and pending_roles; only addresses with a confirmed status can be used to send email campaigns.
- **Create a Constant Contact user** (Create). Add an email address to a Constant Contact account. Returns: email_address, email_id, confirm_status.
- **List all Constant Contact account summary** (List). Get a summary of account details for a Constant Contact user account, including the organization name and account contact information. Returns: encoded_account_id, organization_name, contact_email, contact_phone, organization_phone, first_name, last_name, country_code, state_code, time_zone_id, website, physical_address, company_logo.
- **Constant Contact account summary bulk update** (Update). Update the account details for a Constant Contact account, such as contact, organization, and location information. Returns: contact_email, contact_phone, country_code, encoded_account_id, first_name, last_name, organization_name, organization_phone, state_code, time_zone_id, website.
- **List all Constant Contact activities** (List). List bulk activity statuses in Constant Contact. Returns: activity_id, state, started_at, completed_at, created_at, updated_at, source_file_name, percent_done, activity_errors, status, _links. Max 500 results per page.
- **Get single Constant Contact activity by ID** (Get). Get the status report for a single bulk activity in Constant Contact by id. Returns: activity_id, state, started_at, completed_at, created_at, updated_at, source_file_name, percent_done, activity_errors, status, _links. Required: id.
- **Constant Contact summary company logos bulk update** (Update). Update the company logo for the Constant Contact account. Returns the CompanyLogo object including url, external_url, and internal_id. The logo references either a MyLibrary image (internal_id) or an external image (external_url).
- **List all Constant Contact summary company logos** (List). Get the company logo for the Constant Contact account. Returns the CompanyLogo object including url, external_url, and internal_id, or an empty 204 response when no logo is set for the account.
- **Constant Contact summary physical addreses bulk update** (Update). Update the physical address of a ConstantContact account. Returns: address_line1, address_line2, address_line3, city, state_code, state_name, postal_code, country_code. Required: address_line1, city, country_code. Use state_code for US/CA addresses and state_name for all other countries.
- **Create a Constant Contact summary physical addrese** (Create). Create the physical address for a ConstantContact account. Returns: address_line1, address_line2, address_line3, city, state_code, state_name, postal_code, country_code. Required: address_line1, city, country_code. Use state_code for US/CA addresses and state_name for all other countries.
- **List all Constant Contact summary physical addreses** (List). Get the physical address on record for a ConstantContact account; it displays in the footer of every email sent from the account. Returns: address_line1, address_line2, address_line3, city, state_code, state_name, postal_code, country_code.
- **List all Constant Contact user privileges** (List). List the user privileges associated with your Constant Contact access token as an array of privilege objects. Returns: privilege_id, privilege_name. Includes all privileges, even ones the V3 API does not currently use.
- **Create a Constant Contact default** (Create). Create a new Constant Contact event with default settings, a registration form, and a landing page; it is created in DRAFT status. Returns: description, title, name, event_id, campaign_id, event_start, registration_url, status, and 29 more. No required parameters — name, start_time, end_time, and placeholder_campaign_id have defaults if omitted.
- **Create a Constant Contact event copy** (Create). Create a deep copy of an existing Constant Contact event, including its settings, registration forms, and landing pages; the copy is created in DRAFT status. Returns the new event object including event_id, name, status, event_start, event_end, and registration_url. Required: event_id, target_event_name. DELETED events cannot be copied.
- **Get single Constant Contact event by ID** (Get). Get details for a single ConstantContact event by id. Returns the event object including event_id, title, description, event_start, event_end, status, and registration_url. Required: id, event_id.
- **List all Constant Contact events** (List). List ConstantContact events with event details. Returns: name, event_id, event_start, event_end, status, registration_url. Max 100 per page.
- **Update a Constant Contact event by ID** (Update). Update an event in Constant Contact by id, partially applying only the fields provided in the body (event_settings, location_type). Only events in DRAFT or ACTIVE status can be updated; COMPLETE, CANCELED, and DELETED events cannot. Returns an empty 204 response on success. Required: id, event_start, event_end.
- **Create a Constant Contact check in ticket** (Create). Check in one or more order tickets for a Constant Contact event by marking them as checked in. Returns an empty 204 response on success. Required: event_id, order_ticket_keys. The event must be in ACTIVE or COMPLETE status; CANCELLED tickets cannot be checked in.
- **Constant Contact registrations payment status bulk update** (Update). Update the payment status for one or more event track registrations in Constant Contact. Returns an empty 200 response on success; a 207 reports per-registration results when some fail. Required: event_id, track_id, registration_ids, payment_status. Only registrations with a payment method (PAYPAL, WEPAY, STRIPE, DOOR, CHECK) are processed. Only applies to registrations with a paid ticket; free registrations are rejected.
- **Constant Contact track registrations bulk update** (Update). Update the registration status for one or more registrations in a Constant Contact event track. On success returns a 200 with no body; when some registrations fail to update, returns 207 with failed_registration_ids. Required: event_id, track_id, registration_ids, registration_status.
- **Get single Constant Contact track registration by ID** (Get). Get registration details for a specific event track in Constant Contact. Returns: registration_id, contact_id, checkedIn_tickets, checkin_status, eligible_checkin_tickets, registration_date, registration_status, display_physical_tickets, contact, tickets, order_summary. Required: id, event_id, track_id, registration_id.
- **List all Constant Contact track registrations** (List). List registrations for a Constant Contact event track. Returns per registration: registration_id, first_name, last_name, email_address, registration_status, payment_status, tickets, total, and check-in details. Required: event_id, track_id.
- **Create a Constant Contact undo check in ticket** (Create). Undo check-in for one or more tickets of a Constant Contact event, marking them as not checked in; the event must be in ACTIVE or COMPLETE status. Returns an empty 204 response on success. Required: event_id, order_ticket_keys.
- **Constant Contact segment names bulk update** (Update). Rename an existing Constant Contact segment by updating its name. Returns: name, segment_criteria, criteria, segment_id, created_at, edited_at. Required: segment_id and name.
- **Create a Constant Contact segment** (Create). Create a new Constant Contact segment targeting a subset of contacts for a marketing campaign. Returns: name, segment_criteria, criteria, and 3 more fields. Required: name, segment_criteria. Requires name (must be unique) and segment_criteria as a JSON object; do not exceed 500 email campaigns or a 1825-day date range in the criteria.
- **Delete a Constant Contact segment by ID** (Delete). Delete a segment from ConstantContact by id. Returns an empty 204 response on success. Verify the segment is not associated with a scheduled campaign before deleting. Required: id.
- **Get single Constant Contact segment by ID** (Get). Get a Constant Contact segment by id, including its contact-selection criteria. Returns: name, segment_criteria, criteria, segment_id, created_at, edited_at. Required: id. Details for deleted segments can also be retrieved.
- **List all Constant Contact segments** (List). List all Constant Contact segments in the account, sortable by name ascending or most recently updated first. Returns: name, segment_criteria, criteria, segment_id, created_at, edited_at. Deleted segments are excluded from the results.
- **Update a Constant Contact segment by ID** (Update). Update a Constant Contact segment's name or contact-selection criteria by id. Returns: name, segment_criteria, criteria, segment_id, created_at, edited_at. Requires id, name, and segment_criteria — both body fields must be sent even if only one changes. Required: id, name, segment_criteria.
- **Create a Constant Contact contact custom field** (Create). Create a custom field in Constant Contact to store extra contact data such as preferences or interests. Returns the created field with custom_field_id, label, name, type, metadata, version, choices, created_at, and updated_at. Requires label and type. Accounts support up to 100 custom fields.
- **Delete a Constant Contact contact custom field by ID** (Delete). Delete a custom field from a ConstantContact account by id. Returns an empty 204 response on success. Required: id.
- **Get single Constant Contact contact custom field by ID** (Get). Get details for a single custom field in Constant Contact by id. Returns: custom_field_id, label, name, type, metadata, version, choices, updated_at, created_at. Required: id.
- **List all Constant Contact contact custom fields** (List). List all custom fields defined in the Constant Contact account. Returns each field with custom_field_id, label, name, type, metadata, version, choices, created_at, and updated_at. Max 100 per page.
- **Update a Constant Contact contact custom field by ID** (Update). Update an existing custom field in Constant Contact by id. Returns the updated field with custom_field_id, label, name, type, metadata, version, choices, created_at, and updated_at. Requires label and choices; any omitted properties are overwritten with null. Required: id.
- ...and 81 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
