Skip to main content

Communications MCP: contacts, with addresses always masked

  • 7 new tools on the communications server: comms_list_list_contacts, comms_find_contact, comms_import_contacts, comms_remove_from_list, comms_derive_list, comms_unsubscribe_contact and comms_add_suppression. They use the permissions a connection already has (read:comms and write:comms.audience), so there is no new consent.
  • Addresses are always masked. An agent sees ids, counts and addresses like j***@example.com, names as initials, and never a phone number. For real addresses you open the dashboard.
  • Consent is asked, not assumed. A real import needs the answer to "do these people know they will get your marketing email?", given as true or false. Every write is a dry run first. People who unsubscribed, bounced or are suppressed are never added back.
  • What an agent cannot do: delete or erase a contact, resubscribe anyone, export contact data, remove everything matching a search from a list, or send. Suppressions apply to the whole account.
  • API: POST /lists/derive accepts an Idempotency-Key, like the other creates, so a retried call returns the first list instead of making a second one.

Documentation changed