Gamma integration with lemlist through MCP, with prompts to copy

A prospect replies “interested” in lemlist. Their reply mentions a specific problem, a specific team size, a specific deadline. Your rep sends the same generic deck they send everyone else, and the deal cools off before the next touch.

That gap exists because lemlist and Gamma live in separate tabs. The data that should trigger a tailored deck sits in your inbox instead, and nobody connects the two tools fast enough to use it.

This article fixes that gap with a gamma lemlist integration built on MCP. I’ll show you what to set up, two prompts you can copy today, and the guardrails to keep an agent from acting on bad data. By the end, you’ll know how to turn a reply into a personalized deck without opening a design tool.

Why connect lemlist and Gamma through MCP

An interested reply deserves a personalized deck built for that specific account. When both MCP servers are connected in the same AI client, an agent can read a prospect’s reply in lemlist, pull their company context, and build a short Gamma deck tailored to that account in one conversation.

An MCP server is a standardized endpoint that lets an AI agent call actions inside an external tool. The agent discovers available actions, sends requests, and gets results back, all through the same chat window. If you want a deeper look at how this applies to sales workflows, read the full breakdown on MCP for sales.

Because both lemlist and Gamma expose MCP servers, the agent can chain actions across the two tools without exports, CSVs, or tab switching. It reads outreach data on one side and creates presentation content on the other, inside a single prompt.

What you need before you start

Three things to have in place:

• •

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

• •

  The Gamma MCP connected in the same client, so the agent can generate presentations, documents, and webpages from your prompts.

• •

  Permissions scoped to what each use case needs. Limit the agent’s access to the specific campaign and presentation actions you plan to use.

Start with read-only prompts. Let the agent pull replies and company data before you give it permission to create decks or draft messages. Once you trust the output on a small batch, open write access in both tools.

1. One-pager for each interested reply

Most reps send the same deck to every prospect who replies with interest. The prospect mentioned their specific pain point, and the rep responds with a generic overview that could belong to any company.

When you run this prompt, the agent reads your lemlist unified inbox for replies tagged as interested. For each one, it pulls the prospect’s company name, industry, and the context from their reply. It then calls the Gamma MCP to generate a one-page deck focused on that company’s situation. Finally, it drafts a reply in lemlist with the deck link included. If you want more tactics for handling cold email replies, that guide covers the full playbook.

Before running this on your full pipeline, review two or three generated decks manually. Check that the company details are accurate and the messaging matches your positioning.

2. Account plan before a big meeting

Building an account plan before a strategic meeting usually means pulling conversation history from your outreach tool, searching for company news, and assembling slides by hand. That prep can eat an entire morning.

The agent reads every touchpoint with that account from your lemlist campaign history: emails sent, replies received, LinkedIn interactions. It combines that with company data available through lemlist’s enrichment. Then it calls the Gamma MCP to generate a five-slide deck covering the account summary, engagement timeline, key contacts, potential objections, and a proposed next step. You can pair the deck with a strong demo follow up email to keep momentum after the meeting.

Before letting this run across multiple accounts, verify that the conversation history it pulls is complete and that the slides reflect your actual relationship with the account.

Guardrails when an agent works in lemlist and Gamma

Giving an agent write access to two tools at once means you need clear boundaries. Follow these before scaling:

• •

  Review every campaign the agent creates or modifies before it goes live. The agent can draft and build, but a human approves the launch.

• •

  Test on 10 leads first. Run the prompt on a small batch, check the output, then expand.

• •

  Keep unsubscribes and exclusion lists active. The agent should never override opt-out preferences, and lemlist enforces these by default.

• •

  Decide who on the team can connect the MCPs. Limit MCP access to people who understand both tools and the workflows they power.

• •

  Log what the agent changed. After each session, check which campaigns were updated, which decks were created, and whether any lead data was modified.

These guardrails apply to every prompt in this article. They also apply to any new prompt you write that chains lemlist and Gamma actions.

Run it in lemlist

The lemlist MCP server works in Claude, ChatGPT, and Cursor. Once connected, the agent can do everything you do inside lemlist, through a single conversation.

It can search the People database with 650M+ contacts and 65M+ companies. It can enrich leads with waterfall enrichment across 14+ providers to find verified emails and phone numbers. It can create campaigns and sequences across email, LinkedIn, calls, and WhatsApp. It can read your unified inbox and campaign stats to understand what is working. And it can act on intent signals to prioritize outreach based on real buying behavior.

When you pair these capabilities with a Gamma MCP, the agent goes beyond outreach management. It turns your campaign data into visual assets your prospects actually want to open. You can explore more workflows like this in the full list of lemlist MCP use cases.

Final takeaway

Connecting Gamma and lemlist through MCP lets an agent turn outreach data into personalized decks without manual work. The prompts in this article give you a starting point: one for tailored one-pagers on every interested reply, another for account plans before big meetings. Start with a small batch, review the output, and expand once you trust the results.

Build your first signal-based sequence in lemlist.