Producing an Email Newsletter with MCP: A Step-by-Step Playbook

A regular email newsletter takes more work than it looks. Someone reviews last issue's results, picks the audience, writes the copy, builds the email from a template and schedules the send. In small businesses that is usually the marketing lead or the owner.

MCP (Model Context Protocol) lets an AI app reach your email platform directly. It can pull campaign reports, check lists and segments, and set up a draft campaign from your template. A person still approves the content and presses send.

This playbook uses the official Klaviyo and Brevo MCP servers. Tool names come from each vendor's docs, checked on 28 October 2026. eSEOspace did not install or test these servers. More workflows are in our MCP playbooks hub.

What you need

Klaviyo's connection guide gives the remote URL as https://mcp.klaviyo.com/mcp. It says the feature is "only available to Klaviyo users with an Owner, Admin, or Manager role." Klaviyo recommends the remote server over the local one in its MCP overview.

Brevo's MCP docs list a main endpoint, https://mcp.brevo.com/v1/brevo/mcp, that combines 27 modules. Brevo also lists single-module endpoints, including brevo_email_campaign_management, brevo_templates, brevo_lists, brevo_segments and brevo_campaign_analytics. You create an MCP token under Account > SMTP & API > API Keys, with the MCP option checked.

For the client, any app that supports remote MCP servers works. Klaviyo notes that query parameters "can't be controlled with the listed Claude connector or the listed ChatGPT app," so use a custom connector if you want read-only mode.

The workflow

The steps use Klaviyo tool names from its available tools page. Brevo documents modules rather than tool names, so with Brevo you ask for the same job and the client picks the tool.

1. Review last issue. Pull results for recent newsletters. Klaviyo's get_campaigns finds them and get_campaign_report returns performance; both are read-only. With Brevo, connect the campaign analytics module.
2. Check the audience. Confirm which list or segment the newsletter goes to. Klaviyo has get_lists and get_segments, both read-only. Ask the AI to report the audience you used last time so the new draft matches.
3. Gather content. Collect the stories, offers and links you want to feature. This part comes from you, your blog or your product team, not from the email platform.
4. Draft the copy outside the platform first. Have the AI write the subject line, preview text and body in chat. Edit it there. It is faster to fix copy before it becomes a campaign.
5. Prepare the template. Klaviyo's get_email_template reads a template and clone_email_template copies it, so last issue's design stays untouched. render_email_template is read-only and lets you preview the result.
6. Create the draft campaign. Klaviyo's create_campaign sets up the campaign. assign_template_to_campaign_message and update_campaign_message attach the template and content. With Brevo, use the email campaign management module. Approve each of these write calls.
7. Review in the platform. Open the draft in Klaviyo or Brevo yourself. Check links, images, the audience, the send time and the unsubscribe footer. Send a test to your own inbox.
8. Send by hand. A person schedules or sends from the platform. Klaviyo does offer send_campaign and cancel_campaign_send, but a newsletter that reaches every subscriber should not depend on an AI tool call.

Example prompts

• "Using Klaviyo, list our last six newsletter campaigns and give me the campaign report for each. Which subject lines did best?"
• "Show me the lists and segments we sent the last newsletter to. Don't change anything."
• "Clone our 'Monthly newsletter' email template, then render the clone with this month's copy so I can preview it."
• "Create a draft campaign called 'November newsletter' for the Newsletter list, assign the cloned template and stop. Do not send or schedule."
• "Using Brevo campaign analytics, compare our last three newsletters and list what changed between them."

Guardrails

Start with reporting in read-only mode. On Klaviyo's remote server, set read-only=true to disable every tool that can write. You can also use the toolsets parameter to expose only tools whose scopes you list, such as read access to campaigns. Brevo's docs describe no read-only mode or per-token scopes, so connect only the analytics module at first.

Approve every write call. create_campaign, update_campaign_message and template changes alter your account. Turn on your client's per-call approval and read each call before you allow it. Our lesson on MCP permissions and approvals explains how that works across clients.

Keep sending human. Leave send_campaign out of your toolset or reject it at the prompt. A wrong send cannot be unsent.

Limit user-generated content. Klaviyo marks some tools, including get_profiles, as handling user-generated content. Its URL parameter disable-tools-with-user-generated-content hides them. Klaviyo warns that these tools carry prompt injection risk and advises you to "carefully review each tool call." Read about MCP prompt injection and visit the MCP Security Center.

Protect the token. Brevo's MCP token sits in a request header, and the docs describe no way to narrow what it can do. Store it like a password and rotate it if it leaks.

Keep these human: final copy approval, audience choice, legal and compliance wording, and the send.

What to measure

Use your platform's own campaign reports, before and after you add MCP:

• Time from planning to a ready-to-review draft.
• Number of edits a person made to the AI's draft before approval.
• Errors caught in review, such as broken links or wrong audience.
• Write calls rejected at the approval prompt.
• Your usual newsletter metrics from the campaign report, compared with earlier issues.

Next step

For more marketing workflows, read MCP for marketing teams. If you want help promoting your own MCP product, see our MCP marketing service.

Frequently asked questions