MCP for email marketing: What you can do with Stripo
Despite your email workflow being well established, you may still be spending time searching for old drafts, comparing texts, reviewing briefs, or checking project updates. The Stripo MCP server allows an AI assistant, such as Claude, to read your content in Stripo and help with these tasks without requiring you to first copy each email into a chat. Here, we’ll explore how you can use this feature; as new capabilities become available, we’ll add more examples.
What MCP changes in your email workflow
Model Context Protocol (MCP) is a standard that enables AI applications to connect to other tools. Through Stripo’s MCP server, the AI assistant can find emails, read their content, and export them in HTML format. What it can read depends on the account you connect and the access permissions you grant.
Without this connection, you have to manually provide the assistant with the emails you want it to analyze — you find them in Stripo, copy the text into the chat, and specify which email each snippet comes from. If you later want to add another draft, you’ll need to find and copy that one as well.
With Stripo connected, you can name the emails and ask the AI assistant to read them. The assistant works with the emails, templates, and modules saved in your team’s Stripo library, including content you haven’t pasted into the chat. When comparing two emails, Stripo provides the content, and the assistant analyzes the differences between them. Then, you can choose the email you want to use and make the changes in Stripo.
For example, after comparing two promotions, you might want a closer look at the conditions of one specific offer. The Ai assistant can work with that email in the same conversation. If you want to check it against a new brief, you’ll need to provide that brief as well.
Kitson describes using standard automation when the steps are already known, such as adding a new subscriber to a welcome sequence. When reviewing old emails, you may need to read their content before deciding which email to use or what to ask next.

In the example requests below, replace the names and dates in square brackets with your own.
Find existing content before building another email
You’re launching a reactivation campaign and want to use something the team created earlier. You remember the type of email, but you might not remember its name or folder. Instead of opening every relevant project yourself, you can make the following request: Find all emails with “reactivation” in the name across accessible projects.
The search results provide matching emails for you to review. Other questions include “Do we already have an abandoned-cart template?” and “What do we have for a welcome series?”
You may only need a saved block, such as a footer, rather than an entire email. Stripo MCP can also find saved modules. For example, ask, “Find the module [module name] in [project].” You can then open the matching module in Stripo to check it before adding it to the new email.
What to check: Read the email you find before reusing it, and try another term, such as “win-back,” if that’s what your team calls these emails.
Compare two emails to select a starting point
You may find two emails that are suitable for your new campaign: one has a well-written introduction, while the other presents the offer more clearly. To compare them on your own, you’ll need to switch back and forth between them and note which parts you want to retain. An AI assistant that can read both emails can place these parts side by side for you.
Compare the offers and CTA wording in [email A] and [email B] in [project]. Quote the passages that differ and identify which email each passage comes from.
You can request both the original wording and the assistant’s comments. This enables you to review both offers in one place and understand the action that each call to action asks the recipient to take. It is also helpful when the emails appear very similar but use different terms. For example, one may offer a discount on selected items, while the other offers a discount on the entire order.
Explain to the AI assistant what the new email is intended to achieve. For a campaign targeting people who aren’t yet familiar with the product, you may want to compare how well the introductions describe the product. For a promotion, the main question might be to ask how clear the terms of the offer are. Thus, the same two emails can lead to different choices depending on the objective.
Further, you could use one email with a new offer, or take its introduction and rewrite the remainder in Stripo.
What to check: Check the quoted text against the two emails before deciding which one to use.
Check an email against the campaign brief
Before approving a draft, you need to check that it meets the requirements provided in the brief. You may be reading the requirements in one window and the email in another, taking notes as you go. Even if a detail is present in the email, it may still be wrong for this campaign.
Instead, you could paste the current brief into the conversation and tell the AI assistant which Stripo email to read. The assistant then compares the email with the requirements you’ve provided.
Read [email name] in [project] and check it against the brief below. For each requirement, quote the relevant wording and explain whether it matches. If you cannot find the information, say so.
Brief: [paste the current campaign requirements].
The assistant goes through the requirements one by one and displays the text it found for each. If the email says something different, the response can include the wording you need to check. If a detail is missing, you’ll have a specific question to ask the brief's author or the colleague who prepared the email.
Suppose the brief specifies a discount that expires on a certain date. An earlier promotion may already mention a discount and its expiration date. Both must match the new brief. Ask the assistant to compare the actual offer and date rather than merely confirm whether a discount and deadline are present.
For a requirement such as “friendly tone,” provide an approved example and explain what you want to retain from it. Ask the assistant to indicate where the draft differs from this example. You can then review the wording it points out and decide whether to change it.
What to check: Confirm the findings in the email, then complete your usual visual and link checks before approval.
Catch up on a project after time away
When you return to a project, you may need to find out what your colleagues have been working on while you were away. Reviewing the activity records can help, but you’ll still have to put the updates together and decide which emails to open. An AI assistant can review the Workspace activity available through Stripo MCP and prepare a summary for you.
Summarize the available activity in [project] from [start date] to [end date]. Group the updates by affected item and identify any missing information that prevents you from answering.
This summary can help you compile a list of emails to review before the next team meeting. If there are multiple entries for the same email, the assistant can group them in its answer. You’ll be able to review the updates for that email in one place and decide whether to open it or ask a colleague about the work.
If the summary is long, ask the assistant to show only emails with more than one recorded update during that period. You can begin with these emails when deciding what to review before the next meeting.
What to check: Use Version History to review changes inside the email, and confirm approval with your team.
Get the reviewed email ready for a developer
You’ve just reviewed an email using the assistant, and a developer needs the HTML code to continue working. The email is already identified in the conversation. You can request the code right there, without having to go back to the project and search for the email again.
Export the HTML of [email name] in [project], the email we just reviewed.
Stripo MCP supports exporting a selected email or email template to HTML. You can send this code to the developer along with your notes. If you’ve been discussing multiple drafts, specify the name of the one you’ve selected in the export request.
The developer may also need images as separate files. For this, use the HTML archive export in the editor. Exports through MCP count toward your applicable export quota.
What to check: Ensure the exported HTML comes from the email you gave the developer.
Keep the final decision with your team
Stripo MCP does not schedule or send campaigns; thus, it is important to follow your team’s approval and sending process, including after any edits made through the MCP. To compare campaign performance, you also need results from the system that records them; the email’s content alone cannot tell the assistant how the campaign performed. In addition, deletion should remain a separate request, requiring your confirmation before anything is removed.
Ask the assistant to show you where its answer came from. When reviewing an email, it can point to the relevant sentence in the copy. If it cannot find a detail, ask it to say so.
Wrapping up
Select a task you already frequently perform and try it with emails you’re familiar with. John Gruber, who deploys Microsoft Copilot in enterprise environments, recommends beginning with a single task and adding new functions and access only after the assistant handles it well. For an initial comparison, use two emails you’ve already reviewed yourself. You’ll be able to tell whether the response covers the differences that matter to you and whether it makes the comparison easier.
While Claude is one option, Stripo also connects to other MCP-compatible tools, including Cursor and VS Code. Stripo’s connection guide describes the setup, supported assistants, and access requirements. Once connected, try the request for your selected task and compare the response with your own content.


0 comments