Native MCPWorkflows
In developmentNewsletters through Native MCP
Understand Native newsletters and use an assistant to prepare a sender, grow a mailing list, save drafts and send an approved campaign.
What is a Native newsletter?
#A newsletter is an email you send to people who have agreed to hear from your business. It can announce a product, share an article, invite customers to an event or provide a regular update. In Native, a newsletter has saved content, a subject line, a sender, a mailing list and a delivery record. It is separate from a social post.
MCP lets a connected assistant work with those Native objects from a conversation. The assistant reads your brand voice and relevant products, writes the email, and calls Native tools to save it. When you explicitly ask to send, Native checks the reviewed content, recipients and sender before starting delivery. The assistant does not deliver mail itself.
The pieces that work together
#| Part | What it means |
|---|---|
| Assistant connection | OAuth access to your Native account from ChatGPT, Claude or another supported MCP host. |
| Brand | The Native business whose voice, images, sender settings, contacts and newsletters are used. |
| Sender | The name and email readers see, the address replies go to, and the business postal address in the footer. |
| Mailing list | A named Native audience, such as “Bakery updates”. A contact can belong to more than one list within the brand. |
| Draft and revision | The saved newsletter and the exact numbered version of its content. Editing creates a new revision. |
| Recipient selection | A saved snapshot of eligible people reviewed for a particular revision. Reading a list does not select it. |
| Approval and delivery | Approval records the exact content, recipients, sender and tracking. A separate send action starts or schedules delivery. |
What does “connect the newsletter” mean?
#- Connect the assistant using the ChatGPT, Claude, Grok or other client guide. Sign in with the Native account that has access to your business.
- Choose the workspace and brand. Newsletter tools require ADMIN or OWNER access on that brand and an eligible Native subscription.
- Read
get_newsletter_setup. This reports the actual sender, domain state, test options, signup settings and delivery readiness. - Prepare a sending address and a Native mailing list. A connected assistant does not verify DNS or subscribe anyone.
From your first list to your first newsletter
#Start here
Use Native for Harbour Bakery. Check whether newsletter tools are available and read our newsletter setup. Explain what still needs to be configured. Help me create a “Bakery updates” list, import the permission-based contacts I provide, and save a Norwegian newsletter about our Saturday class. Keep the email as a draft until I have reviewed it.- Set up the sender: confirm the sender name, reply address, postal address and an available sending route.
- Create or choose a Native list. Import contacts you are authorized to add, or enable Native’s signup page so new subscribers can confirm their own email addresses.
- Give the assistant a brief: audience, purpose, language, confirmed facts, product links and preferred images.
- Save the draft in Native. Open the returned
appUrl, check the wording and appearance, and request edits if needed. - Request a test email to your signed-in account. Review the final saved revision and the eligible and excluded recipient counts.
- Approve the exact newsletter and ask to send now or schedule a specific time. Check the returned delivery record afterwards.
- Set up the senderBusiness email, reply-to, postal address, DNS and readiness.
- Fill your mailing listContacts, imports, signup pages, consent and personalization.
- Draft, test and sendSaved revisions, recipient review, approval, scheduling and results.
- Newsletter tool referenceThe 22 tools, their inputs and the state each one changes.
Ways to use it
#| Goal | Example request |
|---|---|
| Product launch | “Use our Native product information and brand voice to draft a launch email. Confirm the price and release date with me.” |
| Event invitation | “Prepare an email for the Workshop updates list with our confirmed date and booking link. Show the draft and recipient count.” |
| Reuse content | “Turn these three approved social posts into a useful monthly email. Link to the original articles.” |
| Grow a list | “Create a list for café news, enable signup with our privacy link, and give me the signup URL for our website.” |
| Move authorized contacts | “Import the consented subscribers in this file into our Native list. Keep unsubscribe and bounce statuses and report the result.” |
Understand each result
#Creating a list sends no email. Importing contacts does not approve a campaign. A draft is not a scheduled send. Approval sends nothing until send_newsletter is called. Provider acceptance does not prove inbox delivery, and unavailable open or click metrics are not zero.
These MCP tools prepare individual reviewed sends and schedules. They do not enable recurring Autopilot delivery. Mailchimp connections are an optional separate workflow; a Mailchimp audience is not automatically a Native list. Blog publishing still needs the relevant CMS integration.
If the newsletter tools are absent, the assistant can still prepare newsletter copy with available Native context. It must explain the limit and must not claim that it saved a Native newsletter, imported contacts or sent mail.
Start with your Native account
Connect an assistant, choose your brand and ask for a first draft. Available tools follow your Native access.
