Lemlist

@Lemlist show me all leads in the Q1 outreach campaign who opened but didn't reply, then export them as CSV

Found 47 leads in campaign 'Q1 outreach' with status 'opened' (no reply). Exported to lemlist_q1_opened_noreply_2024-01-15.csv with columns: email, firstName, lastName, companyName, openedAt, lastActivityDate, and all custom variables. File contains full lead details including engagement timestamps and any enrichment data you've added via variables.

This example combines filtering by engagement state with export functionality. Requires the campaign ID (which the MCP can look up by name) and valid API credentials with read access. Export format choice (CSV vs JSON) affects downstream analysis — CSV works for spreadsheets, JSON preserves nested custom variables.

@Lemlist create a new campaign called 'Product Launch - Enterprise' for our team, then set up a schedule that only sends Monday-Thursday 9am-5pm EST

Created campaign 'Product Launch - Enterprise' (ID: cmp_x7k2m9). Generated default sequence (seq_p4n8j1) and created custom schedule 'Weekday Business Hours EST' (sch_r3t5w8) with send windows Mon-Thu 09:00-17:00 America/New_York. Associated schedule with campaign. Campaign is now ready — add leads via API or CSV import to begin outreach.

This demonstrates campaign creation with custom scheduling constraints. The MCP creates three linked resources (campaign, sequence, schedule) in one workflow. Note that the schedule only controls send timing — you'll still need to populate the sequence with email steps and add leads separately. Lemlist enforces daily send limits per your account tier.

@Lemlist add a 'demo_requested' variable set to 'true' for all leads in the Enterprise campaign who clicked the calendar link in the last 7 days

Identified 12 leads in 'Enterprise' campaign with calendar link clicks since 2024-01-08. Added variable 'demo_requested: true' to each lead: alice@acme.com, bob@techcorp.io, carol@startup.dev, and 9 others. This variable is now available for segmentation in follow-up sequences or for export in reporting. Existing variables on these leads were preserved.

Shows lead enrichment via custom variables after engagement events. This is a write operation that modifies lead records permanently — useful for triggering conditional sequence steps or tagging high-intent prospects. The MCP must fetch leads by activity filter first, then apply variables individually. If you have hundreds of matching leads, expect this to take 30-60 seconds due to rate limits.

When Lemlist MCP makes sense for outbound sales teams

A 6-person sales team running 4-8 cold email campaigns at once needs to spin up new sequences, load leads, and tweak schedules without leaving their AI workspace. The Lemlist MCP wins here if your team already uses Lemlist as the outbound engine and you're tired of tab-switching to add variables or export lead states mid-week. The 30 tools cover campaign creation, lead enrichment, and schedule binding—enough to handle the full setup loop. The threshold: if you're only checking stats or pulling reports once a week, the MCP is overkill; just use Lemlist's dashboard. But if you're iterating on campaigns daily and need to add custom variables or associate schedules on the fly, this MCP keeps the workflow in one place. Best for teams sending 500+ emails per week who treat campaign ops as a daily ritual.

Using Lemlist MCP to handle suppression lists in real time

A 3-person marketing team at a B2B SaaS company gets unsubscribe requests via support tickets and needs to block domains or restore opted-in contacts without opening Lemlist every time. The MCP's unsubscribe tools (add email/domain, delete unsubscribed email) let you handle suppression list updates from the same workspace where you're triaging support threads. This matters when you're moving fast and can't afford to send to a blocked domain by accident. The trade-off: if your unsubscribe volume is under 5 requests per month, manual updates in Lemlist are faster. But if you're processing 20+ requests weekly or need to script bulk domain blocks, the MCP keeps compliance tight without context-switching. Works best when your team treats suppression as a shared ops task, not a once-a-quarter audit.

When to use Lemlist MCP for mid-campaign lead updates

A 4-person growth team runs a drip campaign and discovers halfway through that 30% of leads need a new variable (like job title or company size) to trigger the right follow-up sequence. The Lemlist MCP's 'Add Variables to Lead' tool lets you enrich leads in bulk without exporting a CSV, editing it, and re-importing. You pull the lead list, cross-reference it with your CRM data in the same workspace, then push the variables back to Lemlist—all in one session. The boundary: if you're enriching leads before campaign launch, do it in Lemlist's UI or via a one-time import. The MCP shines when you're reacting to mid-campaign insights and need to update 50+ leads without breaking your flow. Best for teams running experiments where lead segmentation evolves weekly, not quarterly.