Create and manage email campaigns through Poptin MCP, using a pre-made or saved template or user-provided HTML, previewing and saving the right audience, and leaving a verified draft or explicitly con
Turn the user's campaign brief into a verified Poptin campaign. Use the connected Poptin MCP tools, not Gmail or a substitute sending service. Installing this skill does not connect an account or authorize any campaign.
Read the [capability reference](references/capabilities.md) when connecting, resolving a missing tool, or choosing the HTML route. Inspect the currently exposed MCP tools and their input schemas before calling them. Use actual returned account, campaign, audience, property and template IDs; never invent tool names, parameters or IDs.
Verify the authorized account/subaccount, email feature availability, sending setup and the intended sender/reply-to. A connection is scoped to one account. If missing, guide the user through the supported OAuth connection to https://mcp.popt.in/mcp; do not request passwords, API keys or tokens in chat. Do not change credentials, account permissions or DNS as a side effect.
Reuse supplied context. Identify the objective, campaign name, subject/preheader, sender, approved content/offer, CTA, intended recipients and exclusions. Determine whether the user wants a draft, send now, or scheduled send. Ask only for missing facts that block that outcome. If launch intent is unclear, prepare a draft, not a send. This skill never grants standing send permission.
Inspect existing campaigns before creating one. Resume the intended draft rather than duplicating it; preserve human edits and do not alter an already-scheduled or sending campaign without explicit direction. Record its ID after creation. A timeout is not proof that creation failed.
Pre-made or saved template: browse the connected account's available gallery and saved templates, inspect the selected design and use its real ID. Populate the approved copy, links and assets through supported editing tools. Do not overwrite a shared original template when only a campaign copy is intended.
HTML upload: inspect the supplied HTML and its assets first. Use an HTML import/upload/content field only if the currently exposed MCP schema supports it. Never pass HTML into a template-ID field or claim a file was uploaded when it was only drafted locally. If the MCP connection lacks HTML import, prepare checked HTML and give the user the precise Poptin UI handoff; resume with the resulting saved template/campaign ID after it exists. Do not silently substitute a gallery template. See the [capability reference](references/capabilities.md) for the verified boundary.
For either route, preserve unsubscribe and preference controls, required sender details and valid personalization fallbacks. Use Poptin's actual supported merge syntax, not guessed tags. Check CTA destinations, image alt text, mobile layout, subject/preheader and approved offer facts. Do not invent discounts, deadlines or claims. Inspect a rendered preview when available; distinguish source review from actual rendering. Missing content, broken mandatory links or unverified audience eligibility block launch, not saving a clearly identified draft.
Read back the saved campaign and preview its content and audience. Present a concise launch summary: account, campaign ID/name, sender/reply-to, subject, content/design version, audience rules/exclusions, eligible count, and requested outcome. For a schedule, resolve the full date, local time, IANA timezone and UTC equivalent, including daylight-saving ambiguity. Never silently shift a past time to another date.
A request to build the campaign, approve copy, or install this skill is not launch confirmation. If material content, recipients, sender or timing changes after confirmation, show the change and reconfirm. Honor any server-provided confirmation workflow without bypassing it. Test emails are real sends: send only when requested/approved to explicitly verified test recipients, never to the production audience by default.
After a mutation, read the same campaign ID back. For asynchronous operations, follow the returned status/job identifier through supported read tools. Report saved draft, scheduled with the verified time, sending, or completed dispatch, exactly as observed. Accepted requests and SENT/dispatch are not proof of delivery.
On a timeout, denial or ambiguous response, stop further launch attempts. Reconcile the campaign status, job/request ID and logs before considering any retry; never create a replacement campaign to escape uncertainty. Keep an operation receipt in the user's existing authorized work context: campaign ID/link if returned, content version, audience count/preview time, confirmed outcome, request/job IDs and final observed status. Do not store recipient exports or secrets in this skill or a public repository.
Use [scenario checks](references/scenario-checks.md) to evaluate behavior without sending live campaigns.
Weekly roundup of top Claude Code skills, MCP servers, and AI coding tips.