Integration

Plunk integration

Plunk is an open-source email platform. Send transactional emails (now or scheduled, from a template or with your own subject and HTML), reschedule or cancel a scheduled email and read its delivery status, verify an email address, manage contacts and their custom data, list and create templates, create campaigns and send or schedule them to an audience, and list or create segments. Not exposed: event tracking (it only accepts the separate public key), and the routes the API overview only lists in a table without a reference page (reading, updating or deleting a single template, campaign or segment, campaign cancel, test and stats, workflows, events, domains, CSV import, bulk jobs and static-segment membership). Authentication is your Plunk project's secret API key (sk_...), sent as a Bearer token; it works against the hosted service only, not a self-hosted Plunk.

Connect Plunk How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Plunk.Built from the 18 Plunk tools below, on the connection you add once.

What you can do with Plunk

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact, 5 operations

delete_contactDelete contactDELETEPermanently deletes a contact. Plunk answers with no content.
get_contactGet contactGETReturns one contact: email, marketing subscription, snooze end, custom data fields and timestamps (personal data).
list_contactsList contactsGETLists contacts (email, subscription, custom data), newest first by default, 20 per page (up to 100). The first page also carries total; pass the returned cursor to read the next page while hasMore is true.
update_contactUpdate contactPATCHChanges a contact's email address, marketing subscription or custom data fields; fields you leave out are kept. Changing subscribed fires contact.subscribed or contact.unsubscribed, which Plunk workflows can react to.
upsert_contactUpsert contactPOSTCreates a contact, or updates the one with the same email (the answer's _meta.isNew and _meta.isUpdate say which). Pass subscribed explicitly to set marketing consent; custom fields go in data.

Campaign, 4 operations

create_campaignCreate campaignPOSTCreates an email campaign as a DRAFT (nothing is sent) for ALL contacts, a SEGMENT (segmentId) or a FILTERED audience (audienceCondition). Send it with send_campaign or schedule it with schedule_campaign.
list_campaignsList campaignsGETLists campaigns with their status, audience and delivery counts (recipients, sent, delivered, opened, clicked, bounced), 20 per page by default. Filter by status or by text in the name, subject or sender.
schedule_campaignSchedule campaignPOSTSchedules a draft campaign to be emailed to its whole audience at scheduledFor; once sent, each recipient counts as one Plunk email. Returns the campaign with its new status. To send at once, use send_campaign.
send_campaignSend campaignPOSTSends a draft or scheduled campaign to its whole audience immediately; each recipient counts as one Plunk email. To send later, use schedule_campaign instead. Returns the campaign with its new status.

Email, 4 operations

cancel_scheduled_emailCancel scheduled emailPOSTCancels a scheduled transactional email before it goes out; it is kept with status CANCELLED and not billed. Cannot be undone, and a throttled notification it held may then be sent again.
get_emailGet emailGETReturns one email: its status (SCHEDULED, PENDING, SENDING, SENT, DELIVERED, OPENED, CLICKED, BOUNCED, COMPLAINED, FAILED or CANCELLED), source, subject, recipient contact and send times.
reschedule_emailReschedule emailPATCHMoves a scheduled transactional email (sent with delivery.at) to another time; a time not in the future sends it now. Only the time can change: to change the content, cancel it with cancel_scheduled_email and send a new one.
send_emailSend emailPOSTSends a transactional email now, or at delivery.at (up to 30 days ahead), from a template or your own subject and HTML body. Each recipient costs one Plunk email (two with attachments). Returns one email id per recipient for get_email.

Segment, 2 operations

create_segmentCreate segmentPOSTCreates a segment: DYNAMIC (the default) from a filter condition re-evaluated as contacts change, or STATIC, whose members are managed in the Plunk app. Use its id as a campaign audience or in filters.
list_segmentsList segmentsGETLists every segment of the project (not paginated), newest first, with its type, filter condition, membership tracking and cached member count.

Template, 2 operations

create_templateCreate templatePOSTCreates an email template usable by send_email and campaigns. from must be on a domain verified in the Plunk project, or the request is refused. Type MARKETING (the default) adds an unsubscribe footer.
list_templatesList templatesGETLists email templates (name, subject, HTML body, sender, type), 20 per page by default; page through with page and pageSize. Filter by type or by text in the name, description or subject.

Email address, 1 operation

verify_email_addressVerify email addressPOSTChecks one email address without sending anything: validity, disposable or alias domain, free personal provider, plus addressing, DNS and MX records, and likely typos with a suggested correction.

Use Plunk from Claude Code, Cursor or Codex

Connect Plunk in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Plunk operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Plunk

Create your workspace
Sign up free. Nothing to install.
Connect Plunk once
Add your Plunk connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.