Native MCP· Newsletter setup

Native MCPWorkflows

In development

Set up newsletter sending

Connect Native to your assistant, prepare your newsletter sender and understand domain verification, test emails and sending readiness.

Read the existing setup first

#

Text

For Harbour Bakery in Native, read our newsletter setup. Show the prepared sender, reply-to address, postal address, sending-domain status, test options and whether Native list delivery is ready. Explain any missing requirement before changing anything.

get_newsletter_setup reads the selected brand. It returns settings, connection, domain, preview, an appUrl for newsletter settings and a signupUrl. Share the signup URL only after signup has been enabled and its sending prerequisites work.

FieldHow to use it
settings.senderSaved sender choices. An empty reply-to can follow the workspace owner’s current address.
connection.preparedSenderThe resolved sender name, sender email and reply address. Show and copy this exact object into an approval.
connection.nativeTrackingThe tracking Native can actually apply to this sender. Use this exact value for Native approval.
connection.liveDeliveryEnabledWhether live delivery is enabled for the deployment. False blocks real sending and test emails.
connection.nativeDeliveryAvailable / nativeDeliveryReadyWhether Native delivery is configured, and whether this brand’s sender is ready. Neither confirms a campaign was sent.
connection.nativeSignupReadyWhether the sender can support signup confirmation emails. Also check that signup is enabled for the intended list.
domainActual sending-domain availability, state and any DNS records supplied by Native.
previewThe signed-in reviewer email and preview transport availability. A preview option does not verify a production sender.

Choose the sender and reply address

#

The sender name identifies your business in the inbox. The sender email is the address the newsletter comes from. The reply-to receives readers’ replies and can differ from the sender email. The sender postal address is the real business address in the footer. Saving these fields does not verify domain ownership.

Text

Set our newsletter sender name to Harbour Bakery and reply-to to hello@example.com. Set the postal address to the business address I provide. Keep the existing sending mode and tracking choices, then read the setup again so I can check it.

update_newsletter_settings changes only the sections provided. For example, {"sender":{"replyTo":"hello@example.com"}} keeps the current name, sender email and mode. A concurrent change to the same section is rejected rather than overwritten. Read the setup again after saving.

Use an available sending route

#
RouteRequirements and behavior
Your business domain (OWN)Use an address on a domain you control. Native must offer domain setup and verify the required DNS records. Sender details, postal address, transport and live delivery must also be ready.
Your brand on Native’s domain (NATIVE)Where offered, Native resolves an address for the brand. Read the prepared sender instead of inventing an address. Shared daily limits or a sender pause may apply. Open and click tracking is disabled.
Another email serviceNative’s Other email services section can offer separate provider connections. These do not automatically move an external audience into a Native list. These guides use Native lists.

Verify a business domain when setup is offered

#
  1. Confirm the domain you own and want to use. Ask the assistant to call setup_newsletter_sending_domain with it.
  2. Give your DNS administrator or website provider the exact record types, names and values returned by Native. This tool does not edit DNS.
  3. After the records are added, call check_newsletter_sending_domain. DNS changes and verification can take time. A request to check is not a verified result.
  4. Read get_newsletter_setup again. Confirm the intended prepared sender and the reported readiness. Resolve any remaining postal-address, tracking or service requirement before sending.

Do not copy DNS values from a generic example. Native returns records for the actual provider and domain. If setup reports unavailable, stop at that state; no verification has completed.

Connect a mailbox or send yourself a test

#

Native’s “Send yourself a test” flow sends a saved newsletter revision to the signed-in user. The MCP test tool takes a transport choice and stable request id, not an arbitrary recipient address. Where enabled, it can use Native’s Resend preview service or a connected email mailbox through Zernio.

Connect a Google or Microsoft mailbox in Native when you need that preview route, then use its returned account id. The setup response lists usable mailboxes under preview.mailboxes, including their account ids. Connect a missing mailbox in Native, then read setup again. preview.mailboxReadAvailable: false means mailbox status could not be checked. A mailbox test is a preview, not a replacement for configured bulk delivery.

Optional: connect Mailchimp

#

If Native offers Mailchimp and you want that connection, create_newsletter_connect_link returns a browser OAuth URL. Open it yourself, choose the provider account and complete its consent flow. The assistant should hand you the link and read the setup again after you finish. Creating the link does not establish that authorization completed.

Do not paste provider passwords or OAuth secrets into the conversation. You do not need a Mailchimp account for Native’s own lists and its configured Native delivery service.

Next: choose who can subscribe

#

Follow Mailing lists and contacts for imports and signup pages. When the sender and list are ready, continue to Draft, test and send.

Start with your Native account

Connect an assistant, choose your brand and ask for a first draft. Available tools follow your Native access.

Choose an assistant