Skip to main content

Communications MCP: campaign drafts, preflight and a test email to you

  • 5 new tools on the communications server: comms_create_campaign, comms_update_campaign, comms_duplicate_campaign, comms_preflight_campaign and comms_send_test. They use the permission a connection already has (write:comms.content), so there is no new consent.
  • Drafts only. An agent can create and edit a draft and copy any campaign into a new draft. It cannot schedule, cancel or delete a campaign, or set a send time, a timezone or pacing. Every write is a dry run first.
  • An honest preflight. It shows who would receive the campaign and who would not and why, the forecast (an estimate) and every warning, and says plainly when no one would receive it. It sends nothing; it stores a compiled snapshot, and any later change makes it stale.
  • A test email goes to you only. The test send has no recipient field: it always goes to the account owner's own verified address, shown masked, and is rate limited.
  • API: dry_run on POST /campaigns and PATCH /campaigns/{id}/settings, and editing a draft's template_id, list_ids and exclude_list_ids through the settings call. Without them nothing changes for existing integrations.

Documentation changed