Stripe integration with lemlist through MCP, with prompts to copy

A customer cancels in Stripe on Tuesday. Nobody in lemlist knows until someone remembers to check three weeks later, by which point the win-back window has closed. Another account upgrades to a higher plan, and the colleagues sitting next to that buyer never hear from your team at all. The data to catch both moments already exists. It just sits in a tool that outreach never looks at.

This article shows you how to fix that with a stripe lemlist integration built on MCP. I’ll walk through what MCP actually connects, what to set up before you touch a live campaign, and three prompts you can copy right now to turn cancellations, upgrades and active subscriptions into targeted sequences. Each one comes with what the agent does behind the scenes and what to check before you let it run on a full list.

Run these right and billing events stop sitting idle in Stripe. They become the trigger that starts your next campaign in lemlist.

Why connect lemlist and Stripe through MCP

Stripe holds the billing events that should start outreach, and lemlist runs the campaigns that reach the right person. When both tools connect through MCP, an AI agent can read one and act in the other inside a single conversation.

Stripe knows who cancelled last month, who upgraded to a higher plan, and who is approaching a usage limit. Each of those moments is a signal. Without a connection, someone has to export a CSV, clean it, and upload it to a campaign. With both MCP servers connected, the agent reads the signal in Stripe and creates or updates the campaign in lemlist in the same prompt.

An MCP server is a standardized interface that lets an AI agent call actions inside a tool. It follows the Model Context Protocol, an open standard for connecting large language models to external tools. You can learn more about how this applies to outbound in the guide on MCP for sales.

What you need before you start

Three things should be in place before you run any of the prompts below:

• •

  The lemlist MCP connected in Claude, ChatGPT or Cursor. Follow the steps in how to set up the lemlist MCP if you haven’t done this yet.

• •

  The Stripe MCP connected in the same AI client. Stripe hosts its own MCP server and supports OAuth or an agent API key for authentication.

• •

  Permissions scoped to what each use case needs. Give the Stripe connection read access to subscriptions and customers. Give the lemlist connection access to campaigns, leads, and the People database.

Start with read-only prompts that pull data without changing anything. Once you trust the output, move to prompts that write in either tool.

1. Win back cancelled subscriptions

Most teams never reach out to a customer after they cancel. The account churns, the contact sits in a billing system, and nobody follows up because the data lives in Stripe while the outreach lives in lemlist.

Copy this prompt into your AI client with both MCPs connected:

The agent reads cancelled subscriptions from Stripe, pulls the customer email and plan name for each one, then adds those contacts to your win-back campaign in lemlist with the former plan stored as a custom variable. That variable can power a personalized first line or subject line in your sequence. For more ideas on structuring this kind of outreach, see the guide on how to re-engage and convert lost leads.

Before running this on a full list, check the first ten leads the agent adds. Confirm the plan variable is correct and the email matches the right contact.

2. Reach colleagues of customers who upgraded

When a customer moves to a higher plan, their team just voted with budget. That upgrade is a signal that other departments in the same company could benefit from the product too. Most teams miss this because billing data and prospecting live in separate tools.

Copy this prompt:

The agent reads recent upgrades from Stripe, identifies the company behind each subscription, then searches the lemlist People database for contacts in different departments at that company. It creates a campaign with a sequence that references the existing relationship. This is multi-threading in sales triggered by a billing event instead of a manual account review.

Before running on a full list, review the colleague matches and the draft sequence. Make sure the agent picked contacts in relevant roles and that the messaging sounds like your team.

3. Exclude customers from cold campaigns

Sending a cold pitch to someone who already pays you damages trust and wastes a touchpoint. It happens more often than teams admit, because the list of active customers in Stripe and the suppression list in the outreach tool are rarely in sync.

Copy this prompt:

The agent pulls all active subscriptions from Stripe, matches the company domains against leads in your running cold campaigns in lemlist, and removes the matches. No more awkward “we’d love to show you a demo” emails landing in a paying customer’s inbox.

Before running on a full list, spot-check the domain matching. Some companies use different domains for billing and corporate email, so confirm the agent matched correctly on the first batch.

Guardrails when an agent works in lemlist and Stripe

Giving an agent write access to two tools means you need clear rules. Follow these before scaling any of the prompts above:

• •

  Review every campaign the agent creates before you launch it. The agent can build the sequence and add leads, but a human should approve the final version.

• •

  Test on ten leads first. Run the prompt on a small batch, verify the output, then expand.

• •

  Keep unsubscribes and exclusion lists active in lemlist. The agent should never override someone who opted out.

• •

  Decide who on the team can connect the MCPs. Limit access to people who understand both tools and the data flowing between them.

• •

  Log what the agent changed. After each session, ask the agent to summarize every action it took, including leads added, leads removed, and campaigns created or modified.

Run it in lemlist

The lemlist MCP server works in Claude, ChatGPT and Cursor. Once connected, the agent can do the following without leaving the chat:

• •

  Search the People database with 650M+ contacts across 65M+ companies

• •

  Enrich leads with waterfall enrichment across 14+ providers

• •

  Create campaigns and sequences across email, LinkedIn, calls and WhatsApp

• •

  Read the unified inbox and campaign stats

• •

  Act on intent signals to time outreach to the right moment

Every prompt in this article chains Stripe data with one or more of those capabilities. You can find more workflows like these in the full list of lemlist MCP use cases.

Final takeaway

Every billing event in Stripe is a trigger waiting to become outreach. An agent with both MCPs connected turns a cancelled subscription, an upgrade, or an active account into the right campaign action in seconds. Connect the two and let the signals do the targeting.

Build your first signal-based sequence in lemlist.