MCP

Example Prompts

Copy and paste these prompts into Claude Code, Codex CLI, or any MCP-compatible AI to send emails through Constant Contact for Agents. No coding required.

Send your first email

Start with a test email to see how it works. Test emails use the Constant Contact sandbox and do not require a verified domain.

Send a test email using the Constant Contact MCP. Use these details:
- To: your email address
- Subject: "Welcome to my business"
- Body: A brief welcome message for new customers
- Execution class: test
- Idempotency key: test-send-001

Confirm this is a test send before proceeding. Test mode uses the CTCT sandbox domain for delivery.

Create an email draft for my "Summer Sale" announcement. Use the brief:
- Announce 20% off all products for July
- Friendly, professional tone
- Include a call-to-action

Generate professional HTML content and save it as a draft so I can review it before sending.

Send a production email using the Constant Contact MCP with these exact parameters:
- to: recipient@example.com
- subject: Hello from Constant Contact MCP
- body_html: <h1>Hello World</h1><p>Your MCP is working!</p>
- execution_class: full_execution
- explicit_production_confirmation: true
- idempotency_key: production-send-001

Before attempting this production send, confirm with me that my workspace default sender/domain is configured and verified for production (or tell me which production-authorized from address to use).
Confirm this is a production send before proceeding.

Troubleshoot with your AI

When something goes wrong, let your AI investigate and suggest fixes.

My last email send failed. Help me understand:
1. Check my recent sends and their status
2. Look for any errors or delivery issues
3. Explain what went wrong in simple terms
4. Suggest how to fix it before trying again

Use the Constant Contact MCP. Before we do anything:

1. List all the tools you have access to
2. Tell me which ones are safe to try (read-only)
3. Which ones would change data or send emails?
4. What should I confirm with you before proceeding?

Advanced: Build your own workflows

Explore the Constant Contact MCP with me:

1. Read the discovery catalog resource (cc://public-mcp/discovery/catalog)
2. List all available tools and what they do
3. List all readable resources
4. Summarize what capabilities I have and what I can accomplish

Check what email templates or structured resources are available. List any resource templates I can subscribe to or read, and explain what each provides.

Execution class defaults

If you omit execution_class, the server infers it from your content source:

Content source	Default execution class
`brief`, `body_html`, or `body_text`	`preview`
`draft_id` or `emails`	`full_execution` (production-intent)

Set execution_class: "test" explicitly when you want sandbox delivery instead of the draft_id or emails default.

Understanding sender behavior

Different execution classes use different sender domains. This is important for understanding what recipients see in their inbox.

Execution class	Sender domain	Use case
`test`	Internal CTCT domain	Test sends — uses CTCT internal sandbox domain. No domain verification required.
`full_execution`	Workspace default domain	Production sends — uses your workspace default sender when `from` is omitted. Requires a configured, verified workspace default domain and `explicit_production_confirmation: true`. Supply `from` only when using a different production-authorized sender.
`draft` / `preview`	N/A	Generated content only — no email is actually sent.