# lemlist
ID: 02-lemlist
Page: https://gtmmcps.com/tools/02-lemlist
JSON: https://gtmmcps.com/data/tools/02-lemlist.json
Documentation references: https://gtmmcps.com/docs/02-lemlist/
Category: Engagement & Outbound
MCP support: official
Testing: RESEARCHED
API access: paid
Last checked: 2026-09-07
Endpoint check: docs-only; date: 2026-09-04

Multichannel sales engagement platform combining lead database/enrichment, email/LinkedIn/call/SMS sequencing, and a unified inbox.

## MCP links
- https://app.lemlist.com/mcp
- https://developer.lemlist.com/mcp/setup

## Sources
- https://developer.lemlist.com/mcp/setup
- https://www.lemlist.com/pricing
- http://help.lemlist.com/en/articles/4452791-lemlist-plans-and-pricing-overview
- https://developer.lemlist.com/api-reference/endpoints/enrich/enrich-data.md
- https://app.lemlist.com/mcp

## Research notes
One of the more clearly first-party, well-documented MCP implementations in this category - dual OAuth/API-key auth, 40+ documented actions. "Advanced API access" is explicitly called out as an Enterprise-tier ("Outreach Scale," 5+ seats, annual billing) feature; standard-tier API availability is not clearly documented, so treat access as paid/enterprise-leaning. 2026-09-03: vendor docs state the Enrich Data endpoint (POST /enrich) accepts firstName, lastName and companyName or companyDomain with a linkedinEnrichment flag ("Run LinkedIn enrichment") and its sample response returns linkedinUrl (https://developer.lemlist.com/api-reference/endpoints/enrich/enrich-data.md); no MCP tool name and no unit price are stated there. 2026-09-07: https://app.lemlist.com/mcp returned 401 to an MCP initialize POST (https://app.lemlist.com/mcp).

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.

## CLI evidence
Status: community
- Reported install command: npm install -g @lemlist-official/cli; source: https://www.npmjs.com/package/@lemlist-official/cli

Read current vendor documentation before configuring or running commands.