Skip to main content

Communications MCP: templates, the brand kit and list cards can be written

Motorical
  • 8 new write tools on the communications server: comms_create_template, comms_create_template_from_starter, comms_update_template, comms_apply_template_fixes, comms_duplicate_template, comms_set_brand_kit, comms_create_list and comms_update_list. They need write:comms.content (templates and the brand kit) or write:comms.audience (the list card).
  • Safe by construction. Every write is a dry run unless the agent passes dryRun: false. Creates carry an idempotency key, so a retry never makes a second copy. Updates return the previous values so they can be undone. Nothing deletes, imports contacts, schedules or sends.
  • One consent line. Reading and the two edit scopes now show as a single line on the consent screen: "View and edit your lists, contacts, templates and campaign drafts, and send test emails to you. This never emails your contacts." Sending keeps its own, separate line. A connection approved earlier keeps working read-only and is asked once for the missing permission when a write tool is first used.
  • API: expected_updated_at on PATCH /templates/{id}. Edit only the version you read; a template that changed since is not overwritten (409 STALE_TEMPLATE).
  • API: strict and dry_run on POST /lists and PATCH /lists/{id}. strict refuses a weak list card (422 LIST_CARD_INVALID); dry_run checks without writing. Without them nothing changes for existing integrations.

Documentation changed