Lemlist MCP connector
The Lemlist connector brings your outreach campaigns, sequence steps, sending schedules, senders and campaign stats into Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client, so your team can run and report on Lemlist outreach by asking in plain language.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Lemlist campaigns are paused across the sales team?
Working in Lemlist with Elaichi
-
List all Lemlist teams
-
List all Lemlist team senders
-
List all Lemlist team credits
How to connect Lemlist to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Lemlist MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Lemlist MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Lemlist MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Lemlist MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Lemlist MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Lemlist to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Lemlist through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Lemlist is logged.
-
Sales
Pause a campaign before a big announcement
Ask which Lemlist campaigns are still sending to a target account and pause them in one go, so nobody gets a cold email the morning your contract lands.
-
Sales development
Rewrite a sequence step that is underperforming
Pull the stats for a Lemlist campaign, spot the step where replies drop off, and update that step's copy without opening the campaign editor.
-
Marketing
Set up a new campaign for an event
Create the Lemlist campaign, add the sequence steps and attach a sending schedule for a conference follow-up, all from one conversation.
-
Revenue operations
Report on outreach stats every Monday
Ask for opens, replies and bounces across every active Lemlist campaign and get a summary you can paste into the pipeline review.
-
Sales leadership
Check who is sending and how much
List the senders on each Lemlist team, see how many credits are left, and find out which reps have campaigns running before the quarter closes.
-
Operations
Move sending schedules for a holiday week
Update the Lemlist schedules so outreach skips the days the office is closed and picks up again on the right time zone.
Try asking
- “Which Lemlist campaigns are paused across the sales team?”
- “Summarize last week's Lemlist campaign reports by sender.”
- “List sequences and schedules for our EMEA outbound campaign.”
What connecting Lemlist gets you
6 screens from Elaichi, each doing one job for your Lemlist account.
Ask Elaichi to work across your apps.
Which Lemlist campaigns are paused across the sales team?
Summarize last week's Lemlist campaign reports by sender.
List sequences and schedules for our EMEA outbound campaign.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Lemlist campaigns in plain language.
Answers come from live Lemlist campaigns, sequences and reports, not stale exports.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Lemlist.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
81 Lemlist tools ready without custom code.
Campaigns, sequences, schedules, senders and team credits, each with its own methods.
Toolboxes
Every team gets its own Lemlist toolbox.
Curate one toolbox per team so each sees only relevant Lemlist tools.
Shared connections
Teammates use Lemlist accounts without credentials.
See who connected each Lemlist account and how many teams and members share it.
Audit log
Every Lemlist call is written down.
When, who, what happened, type and resource for each campaign and sequence action.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Lemlist digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch campaigns
Lemlist
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Lemlist
Queued
Automations
A schedule fires, a Lemlist digest ships.
Fetch campaigns, group them, draft a digest, approve it, post back to Lemlist.
Lemlist health
Refreshed 4 minutes ago · every 15 minutes · from the campaigns collection
Campaigns
1,284 ↓ 12%
Sequences
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Campaigns created
Last 14 days
By team
Share of activity
Outbound EMEA 34%
Outbound AMER 27%
Sales development 21%
Marketing 18%
Collections and dashboards
Lemlist campaign health, counted on schedule.
Four metrics, 14 days of campaigns created and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Lemlist
All three can connect Lemlist to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Lemlist tools | Allow or restrict single Lemlist tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Lemlist call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Lemlist tools for your AI agents
81 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lemlist, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Lemlist to Claude?
Connect Lemlist in Elaichi first, which asks you to paste the API key from your Lemlist settings, and that is the whole sign-in step. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and your Lemlist campaigns, schedules and stats are available in the chat.
Does Lemlist work with ChatGPT and Cursor as well as Claude?
Yes. Once Lemlist is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Lemlist once and every client picks it up, with the same person-level access and the same audit log.
What can an AI agent actually do with my Lemlist data?
It can list your Lemlist campaigns, pull their stats and reports, create or update a campaign, pause one, and add, rewrite or remove sequence steps. It can also create and change sending schedules, and show you the senders, credits and CRM users on each Lemlist team. Short, specific asks such as "pause the Q3 partner campaign" get better results than long paragraphs, because the agent searches for the right action rather than reading a menu.
Does connecting Lemlist give the AI access to every team and campaign?
No. Every call to Lemlist runs as the person who signed in, so the AI only sees the Lemlist teams, campaigns and senders that person can already reach. Elaichi can narrow that further, for example to viewing stats only, but it can never widen it beyond what Lemlist itself allows that person.
Can I stop an agent from deleting or changing things in Lemlist?
Yes. Restrictions in Elaichi work per action, so you can allow reading Lemlist campaign stats while restricting deleting schedules or editing sequence steps. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
What happens to a Lemlist connection when someone leaves?
Offboarding that person in Elaichi ends their Lemlist access at once across every client they used. If they had shared a Lemlist connection with a team, it keeps working for everyone else. Disconnecting Lemlist once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other connected client at the same time.
Does the Lemlist MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Lemlist is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Lemlist?
Yes. Both let Claude, ChatGPT or Cursor use Lemlist. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Lemlist call.
How is Elaichi different from Composio for Lemlist?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Lemlist: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Lemlist in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot