Sales Enablement
Lemlist MCP connector
The Lemlist connector brings your outreach campaigns, sequence steps, sending schedules, senders and campaign stats into Claude, ChatGPT, Cursor or any MCP client, so your team can run and report on Lemlist outreach by asking in plain language.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Lemlist to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Lemlist once
-
Open Connections, choose Add connection, and pick Lemlist.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Lemlist API key. One person generates a token in Lemlist and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Lemlist to 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.
Connect Lemlist to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect Lemlist to 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.
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.
Use cases
What teams do with Lemlist through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting Lemlist gets you
6 screens from the product, each doing one job for your Lemlist account.
The agent
Ask about Lemlist campaigns in plain language.
Answers come from live Lemlist campaigns, sequences and reports, not stale exports.
- campaigns
- sequences
- schedules
- senders
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Lemlist.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
81 Lemlist tools ready without custom code.
Campaigns, sequences, schedules, senders and team credits, each with its own methods.
- List all Lemlist teams
- List all Lemlist team senders
- List all Lemlist team credits
- List all Lemlist team CRM users
Toolboxes
Every team gets its own Lemlist toolbox.
Curate one toolbox per team so each sees only relevant Lemlist tools.
- Outbound sales
- Sales development
- Marketing
- Revenue operations
Shared connections
Teammates use Lemlist accounts without credentials.
See who connected each Lemlist account and how many teams and members share it.
- Outbound EMEA
- Outbound AMER
- Sales development
- Marketing
Audit log
Every Lemlist call is written down.
When, who, what happened, type and resource for each campaign and sequence action.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a Lemlist digest ships.
Fetch campaigns, group them, draft a digest, approve it, post back to Lemlist.
Lemlist digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Lemlist
Queued
Collections and dashboards
Lemlist campaign health, counted on schedule.
Four metrics, 14 days of campaigns created and a breakdown by team.
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%
FAQ
Frequently asked questions
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, 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 blocking deleting schedules or editing sequence steps. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.
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 and every other connected client at the same time.
Put Lemlist in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.