lemlist MCP server
lemlist in any MCP client, through Memtro: lemlist does not publish this server. Memtro's lemlist connector reads lemlist through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
lemlist outreach: campaigns and their status, a campaign's leads, the activity campaigns produce (sent, opened, replied, bounced), campaign stats for a period, contacts and the team's senders; can add a lead to a campaign, send an email from the inbox, create, pause, resume or archive a campaign, pause, resume, mark or unsubscribe a lead, delete a contact, add a note to a contact or company, or create a manual task.
Reads
lemlist_list_campaignsLemlist campaigns: name, status (running, draft, paused, ended, archived, errors), when created and by whom, labels.lemlist_list_campaign_leadsLeads in one lemlist campaign, newest first: lead id, contact id, state and when added.lemlist_list_activitiesWhat lemlist campaigns did and what came back: emails sent, opened, clicked, replied, bounced, LinkedIn steps and so on, each with the lead…lemlist_campaign_statsTotals for one lemlist campaign over a period: leads, leads launched, messages sent and delivered, opens, clicks, replies, bounces, meetings booked.lemlist_list_contactsContacts in lemlist's contact store: name, email, company and job title.lemlist_list_sendersThe lemlist team members who can send, with their email mailboxes (mailbox id and address) and any channel problems.
Acts, when you ask
These change something in lemlist. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
lemlist_create_contact_noteAdds a note to a contact in lemlist, as if written in the app (so it is also pushed to the team's connected CRM, if any).lemlist_create_company_noteAdds a note to a company in lemlist.lemlist_create_taskCreates a manual task in lemlist on a contact, company or lead, assigned to a lemlist user, with a due date.lemlist_add_lead_to_campaignAdds a person as a new lead in a lemlist campaign.lemlist_send_emailSends an email now from a team member's lemlist mailbox to one contact or lead; the contact receives it at once, it cannot be recalled…lemlist_create_campaignCreates an empty lemlist campaign (an empty sequence and the default schedule) for the team…lemlist_pause_campaignPauses a running lemlist campaign, so no further steps go out to its leads until it is resumed; does nothing if it is not running.lemlist_resume_campaignResumes a paused lemlist campaign, so its sequence starts going out to its leads again (people outside the company receive emails and other steps).lemlist_archive_campaignArchives a lemlist campaign, pausing it first if running, so nothing more is sent and it leaves the active list; it can be unarchived in lemlist…lemlist_mark_leadMarks a lemlist lead as interested or not interested, in every campaign it is in…lemlist_pause_leadPauses a lemlist lead, in one campaign or (without campaign_id) in every campaign, so no further steps go out to them until resumed.lemlist_resume_leadResumes a paused lemlist lead, in one campaign or (without campaign_id) in every campaign, so the sequence starts reaching them again.lemlist_unsubscribe_leadUnsubscribes a lead from one lemlist campaign by email, so the campaign sends them nothing more; other campaigns are not affected.lemlist_delete_contactPermanently deletes a lemlist contact together with its leads in every campaign, opportunities, list memberships, inbox conversations and activities…
Connect it
First connect lemlist on Dashboard → Connections, then add Memtro to your client once. The lemlist tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared lemlist connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Who replied to our campaigns this week?
- › How did the Q4 founders campaign do over the last 30 days?
- › Which campaigns are paused or have errors?
- › Which leads bounced in the Northwind outreach campaign?
- › Pause the Northwind outreach campaign until Monday
Questions
- Is this an official lemlist MCP server?
- No. It is Memtro's MCP server with Memtro's lemlist connector behind it: the connector reads lemlist through its API with the credentials you connect on Dashboard → Connections, and lemlist publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in lemlist?
- Only when you ask, and only what it has been granted: add a note to a contact; add a note to a company; create a manual task on a contact, company or lead; add a lead to a lemlist campaign; send an email to a contact from a lemlist inbox; create a lemlist campaign; pause a lemlist campaign; resume a paused lemlist campaign; archive a lemlist campaign; mark a lemlist lead as interested or not interested; pause or resume a lemlist lead; unsubscribe a lead from a lemlist campaign; delete a lemlist contact and everything attached to it. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.