Constant Contact MCP Server

Constant Contact

Constant Contact is an email marketing platform. Teams manage subscribers, lists, tags, segments, campaigns, and send performance from one account.

First moves

1. Account summary — organization name, plan, and audience size before deeper reads.
2. Contact lists — discover list ids and membership counts when structuring audiences.
3. Tags — inventory labels applied to subscribers for segmentation.
4. Contacts — page subscribers or open one contact by id; filter by email or subscription status when provided.
5. Segments — review saved audience filter definitions.
6. Campaigns — list recent email sends; open one campaign for subject, status, and activity ids.
7. Engagement summaries — roll-up sends, opens, clicks, and bounces per campaign activity.
8. Activity tracking — opens, clicks, or bounces detail rows once you hold a campaign activity id.

Data model

Account → Lists / Tags / Segments → Contacts → Campaigns → Campaign activities → Tracking reports. Contacts can belong to multiple lists and carry multiple tags. Each sent campaign exposes one or more campaign activity ids used for performance drill-down.

Operational order

1. Start with account summary or list inventory when list ids are unknown.
2. Resolve contact ids from list or email filters before updating or tagging individuals.
3. For campaign performance, list campaigns or summaries first to obtain campaign activity ids — stats and tracking reads require those ids.
4. Audience hygiene — create or rename lists, add or remove list membership, tag contacts, or delete unsubscribed records when reorganizing.
5. Campaign drafting — create or update campaign content before scheduling; scheduling is a separate confirmed write.
6. Do not guess contact, list, tag, or campaign ids — take them from list responses.

Audience management

List cleanup workflows inventory lists with counts, merge or rename containers, and remove empty lists. Tag workflows list tags with optional usage counts, create new tags, and apply tags to contact sets. Segment reads show saved filter logic for dynamic audiences — membership changes still flow through contacts and lists.

Campaign workflows

Performance reviews pull summary stats across recent sends, then drill into opens, clicks, or bounces for the best or worst activity. Content updates happen on draft campaigns; scheduling a send delivers real email to subscribers and requires confirm_write after the user approves date and time.

Gotchas

• Pagination — large audiences and long campaign histories need repeated list calls with limit and cursor-style paging.
• Activity ids — tracking and summary drill-down tie to campaign activity ids, not the top-level campaign id alone.
• Schedule irreversibility — once a scheduled send passes its window, cancellation may not be possible — confirm datetime with the user before approving.
• Aggregate vs row reports — summary endpoints return roll-ups; per-recipient tracking is available only on activity tracking reads.
• Subscription status — respect active, unsubscribed, and removed filters when the user asks about mailable audiences.
• Writes need confirmation — scheduling campaigns and destructive deletes expect explicit approval.