You can run lemlist from inside Claude or ChatGPT. Connect the lemlist MCP server once, a two minute job with no code, and your AI assistant can find leads, build sequences, read replies and audit campaigns inside your own lemlist account, with a confirmation step before anything sends. Here is the exact setup for both assistants, the first prompts worth running, and the guardrails to set before you hand an AI the keys to your outbound.
What is the lemlist MCP server?
MCP (Model Context Protocol) is the open standard that lets AI assistants operate other software. lemlist shipped its MCP server in March 2026 and has been expanding it since. As of November 2026 it exposes more than 40 actions across prospecting (lead search and enrichment against lemlist's database), campaign building, deliverability checks, inbox and replies, and reporting, per lemlist's setup docs. The connection itself costs nothing extra. Your normal plan limits and credit costs apply, and it works on the free trial.
In practice, you type plain English and the assistant does the clicking. Ask Claude which of this year's "not now" replies are worth a Q4 follow-up, and it reads the replies in lemlist, groups them by objection and drafts a follow-up for each group. Ask why a campaign is flopping, and it audits the last 30 days and points at the one change worth testing. We covered the same pattern for a competing sender in our Smartlead and Claude walkthrough; lemlist's version is the most complete MCP we have tested on the sequencer side.
How do you connect lemlist to Claude?
OAuth is the recommended route:
- In Claude, open Connectors and choose Add custom connector.
- Name it lm. Keep "lemlist" out of the name: it is reserved, and registration fails with a reserved-name error if you use it.
- Paste https://app.lemlist.com/mcp as the URL and save.
- On first use a consent page opens in your browser. Pick your lemlist team and authorize. Tokens refresh automatically after that.
Prefer an API key? Generate one in lemlist under Settings, then Team, then Integrations, and add it as an X-API-Key header in Claude Desktop's developer config. The setup docs have copy-paste configs for Claude Desktop, Claude Code, Cursor and Codex.
How do you connect lemlist to ChatGPT?
- Open Plugins from the sidebar and search for lemlist.
- Install the official lemlist plugin and sign in to your lemlist account when prompted.
- No official plugin available to you? Add it manually: on the Plugins page choose Add custom MCP server, enter https://app.lemlist.com/mcp, pick OAuth and install the plugin it creates.
Whether you can install plugins or custom MCP servers depends on your ChatGPT plan, workspace settings and role, so as of November 2026 some team workspaces will need an admin to approve it.
What should you run first?
Three prompts that earn their keep on day one:
- The audit: "Analyze my campaigns from the last 30 days. Which had the best reply rates, and what should I change on the rest?" You get a diagnosis instead of a dashboard.
- The reply mine: "Find everyone who replied 'not now' or 'bad timing' this year, group them by reason, and draft a re-engagement email for each group." This is the fastest pipeline you will build this quarter.
- The build: Describe your ICP and your angle, and have it draft a multichannel sequence with personalization variables and timing, then review it in lemlist before launch.
Output quality tracks prompt quality. If your prompts are the weak link, Promptbuildr writes stronger ones in about a minute.
How do you keep it on a leash?
Three guardrails matter before you let an assistant near live campaigns:
- Confirmations are built in. Any action that sends messages, spends credits, deletes data or changes campaigns asks you first. Leave that on.
- Scope the tool list. Append a bucket parameter to the connector URL to advertise only what you want used, for example https://app.lemlist.com/mcp?bucket=insights for reporting work or ?bucket=prospecting,crm for list building. One caveat from the docs: buckets control what is advertised, not access, so for a hard restriction scope the API key itself.
- Watch the credits. Email finding, verification and phone enrichment burn credits, and the assistant warns you before spending them. Set expectations with anyone else on the team connecting it.
If you are weighing a native connector like this against building your own, our build-or-buy guide to MCP connectors covers when each makes sense.
Frequently asked questions
Does the lemlist MCP cost extra?
No. As of November 2026 there is no fee for the MCP connection itself. Your lemlist plan limits and credit costs still apply, and it works on the free trial.
Can it send emails without my approval?
No. Sending, spending credits, deleting data and changing campaigns all require your confirmation in the chat before they run.
Which AI assistants does lemlist MCP support?
Claude (including Claude Desktop and Claude Code), ChatGPT, Cursor and Codex have documented setup paths, and other MCP-compatible clients generally work with the same server URL.
Is there a way to limit what the AI can touch in lemlist?
Yes. Use the bucket parameter on the connector URL to narrow the advertised tools, and scope the API key for a hard limit. Separate keys per use case is the clean pattern.
Want outbound that runs while you sleep, with a human still signing off? That is exactly what we build. See The Prospector, our prospecting agent build, and we will wire lemlist, your CRM and your AI assistant into one system.
