Before you build another email: How the Stripo MCP server can help you find existing content
As a shared email library grows, names, folders, and team memory become unreliable ways to see what your team has already built. Imagine that a request for a reactivation campaign arrives. Before building another email, you want to reuse existing work, but one asset may be called “Reactivation,” another “Win-back,” and a third may have a title in another language. Each could sit in a different accessible project or folder.
The problem is not one poor naming choice. Contributors follow different naming habits, projects and folders may split the library, and older files remain alongside current ones. In one public discussion, a multi-brand team reported creating 121 marketing email templates in three months. In another discussion about template searches, contributors described scrolling through several pages and struggling to distinguish between similar names without folder context. When a team cannot confidently identify the right asset, rebuilding may feel safer than reusing the wrong one, and another similar email enters the library.
How teams search before deciding to rebuild
Most existing search methods work best when you already know part of the answer, such as the name of the project, folder, title, owner, or platform.
Project, folder, and title search
You open the project most likely to contain the email, check the expected folder, and search for a word you remember from the title. If it is not there, you repeat the process in other locations. This works well when you know the asset’s name or location but is less helpful when your starting question is broader: “Have we created this type of campaign before?”
Naming rules, tags, and external indexes
Teams often introduce naming conventions, tags, folder structures, spreadsheets, internal documentation, or lists of links shared in team chats. These systems can make content easier to find, but contributors must maintain them whenever they create, move, rename, or update an asset. If that work stops, the index becomes another place that may contain outdated information.
Search inside the product that stores the email
A built-in search depends on the product’s context. An ESP-centered platform searches campaigns, templates, and related objects in the sending environment. An embedded editor solution searches the assets available to that implementation. A template-operations platform or email production workspace searches its own repository and metadata. Each approach can help within the product boundary, but it cannot search for context that the product does not store.
An AI assistant without workspace access
A general AI assistant can suggest search terms or analyze names and content pasted into the conversation. It cannot know which emails, email templates, or modules are present in your Stripo workspace, where they are stored, or which version the team last updated unless it can access that product context.
For AI to answer based on real production content, it needs controlled access to the system where that content lives.
What MCP changes
MCP gives an authorized AI client a standard way to use the data and actions exposed by a connected product. The Model Context Protocol connects AI applications with external data sources and tools, which allows the client to request product information instead of relying only on what you paste into the conversation.
For the reactivation case, the AI client can send an allowed search request to the connected Stripo workspace and return the workspace details provided by Stripo’s released tools. Access remains tied to the connected account and the authorization approved during setup.
What the Stripo MCP server currently lets an AI client do
The current integration can help an AI client find and inspect existing Stripo content before you decide what to build. It can identify the connected account context, find projects and folders, and search or read emails, email templates, and modules. For date-based requests, it can check the server time and workspace activity. Separate requests can export a selected email or email template to HTML or delete selected content.
For the workflow in this article, searching and reading are the relevant actions. The released MCP integration does not provide a public workflow for generating, cloning, editing, or updating an email, nor does it schedule or send campaigns. Export and deletion remain outside the discovery request. The Help Center guide explains how to connect a supported AI client.
What still needs a marketer’s judgment?
Finding an asset does not prove that it is approved, current, relevant, or ready to reuse. After the AI client returns a possible match, you still need to check the target audience, brand, market, language, offer, links, legal terms, and approval status. These checks will determine whether the team should reuse the asset, adapt it through the normal production workflow, or build a new email.
If several items appear relevant, the client should show the alternatives instead of selecting one without your confirmation. Deletion should remain separate from the search and require a clear approval step. The official MCP specification states that people must understand and consent to data access and operations, with human control over the actions a connected tool performs.
Can the Stripo MCP server find an existing reactivation email?
Yes. A connected AI client can search across the Stripo projects available to the connected account for emails with “reactivation” in the name.
The request can be written in plain language:
Find all emails with “reactivation” in the name across accessible projects.
The client will then search across multiple projects or folders and return the matching items for review. It will not decide which email is current or suitable for the new campaign. If your team uses different terms, you may need to repeat the search with another known phrase, such as “win-back,” rather than expecting the client to interpret every variation automatically.
The same search tools can support other questions about existing content:
- “do we already have an abandoned-cart template?”;
- “what do we already have for a welcome series?”;
- “which templates have not been edited for more than a year?”.
Wrapping up
When a reactivation request arrives, you do not have to begin by opening likely projects and folders one at a time. A connected AI client can search the Stripo content available to your account and return the existing assets that may fit the campaign. The value here is not another way to generate an email; it is a way to check the team’s production library before adding another asset to it.
The search result is still only a starting point. You review the available matches, confirm that the selected content is current and approved, and then decide whether to reuse it, adapt it through the normal production workflow, or build a new email.
0 comments