lemlist's MCP server lets Claude work directly with your lemlist workspace — audit campaigns, create and update sequences, and manage leads — over a secure connection. It's available to all lemlist users, works across the major AI clients, and connects with either OAuth or an API key.
This guide covers connecting lemlist to Claude, what you can do with it, and how to slot a data layer into the workflow.
What is the lemlist MCP server?
The lemlist MCP server exposes your lemlist workspace to AI clients over MCP (JSON-RPC over HTTP). Once connected, Claude can audit your campaigns, build or edit multichannel sequences, and manage leads — without you switching between tools. Because lemlist is a multichannel platform (email, LinkedIn, calls), the MCP is useful for orchestrating cadences, not just email.
It works in Claude Desktop, Claude Code, and Cursor, and it's available on every lemlist plan.
How to connect lemlist to Claude
lemlist supports two authentication methods — pick based on your setup:
- OAuth (no API key): cleanest for most users. You authorize in the browser.
- API key: generate one in lemlist settings if your client needs it.
To connect:
- Open your AI client's MCP settings (Claude Desktop, Claude Code, or Cursor).
- Add the lemlist MCP server using the URL from lemlist's developer docs.
- Authenticate with OAuth (sign in and approve) or paste your API key.
- Confirm — lemlist's tools are now available to Claude.
In Claude Code:
claude mcp add --transport http lemlist <lemlist-mcp-url>
What you can do with lemlist in Claude
- Audit a campaign — "Review my Q3 outbound campaign and flag steps with low reply rates."
- Create or update sequences — build a multichannel cadence (email + LinkedIn) from a prompt.
- Manage leads — add, update, and organize leads across campaigns.
- Pull performance data to decide what to change next.
lemlist's multichannel angle means you can ask Claude to reason across email and LinkedIn steps together, which pure email tools can't do.
Where enrichment fits
lemlist includes a lead database, but for verified emails and direct mobiles at high hit rates — especially internationally — a dedicated waterfall layer wins. Run FullEnrich in the same Claude session through its MCP to enrich and verify before you load leads into a lemlist sequence. Enrich with FullEnrich, run the cadence in lemlist.
Gotchas
- Choose one auth method (OAuth or API key) and stick with it per client.
- Actions write to your live workspace — review sequence and lead changes before confirming.
- It orchestrates lemlist; it won't warm up inboxes or replace a dedicated data provider.
Is the lemlist MCP worth setting up?
For lemlist users running multichannel outbound, yes — auditing campaigns and editing sequences from Claude is faster than clicking through the builder, and OAuth setup is quick. Pair it with a waterfall enrichment MCP so your leads are verified before they enter a cadence.
See our best MCP servers for sales roundup and our full lemlist review.