# lemlist MCP (remote): an MCP server we run in production

Canonical: https://scalably.io/mcp/lemlist-mcp
Source: https://app.lemlist.com/mcp
Registry: not published to the MCP registry
Provenance: third-party server, pinned at mcp-remote 0.8.2, verified 2026-10-02. Newer upstream available: mcp-remote 0.14.3; the pin stays at mcp-remote 0.8.2 until it is re-verified.
Integrity: no independent hash is published for this third-party listing; the raw endpoint at https://scalably.io/mcp/lemlist-mcp.md mirrors this representation byte for byte
This is the machine-readable representation of the page at the canonical URL. Same facts, denser format.

## Direct answer
Outreach campaign data from lemlist's hosted MCP, bridged over stdio with mcp-remote.

## Install
- Claude Code: `claude mcp add --transport http lemlist https://app.lemlist.com/mcp`
- Codex: `codex mcp add lemlist --url https://app.lemlist.com/mcp`
- Claude Desktop: not available for this server.

## Environment
| Variable | Required | Secret | Purpose |
|---|---|---|---|
| `LEMLIST_API_KEY` | yes | yes | API key, passed to mcp-remote as the X-API-Key header (OAuth is the vendor's recommended alternative) |

## Tools
The vendor doesn't publish a fixed per-tool list for this server; the tool groups are described under Setup.

## Setup
- Server: `https://app.lemlist.com/mcp` over HTTP. lemlist recommends OAuth; an API key is the alternative.
- API key: app.lemlist.com, Settings, Team, Integrations, Generate. It travels in the `X-API-Key` header.
- Our stdio bridge is the setup lemlist documents as legacy mcp-remote: `npx mcp-remote https://app.lemlist.com/mcp --header "X-API-Key: ${LEMLIST_API_KEY}"`.
- Narrow what the server advertises with `?bucket=` on the URL: `core`, `builder`, `prospecting`, `crm`, `engagement`, `deliverability`, `insights` (comma-separated). `core` is always included: campaigns and team context, settings, memory, help-center search and a generic `call_api` tool.

lemlist doesn't publish a fixed tool list (the tool set "evolves regularly"), so this page lists capability areas rather than tool names: campaign management, lead management, lead sourcing, email enrichment, team and stats, webhooks, and message templates and snippets.


## Limits
- Some operations spend lemlist credits: email finding, verification and phone enrichment.
- `?bucket=` controls what the server advertises, not what the key is allowed to do. Scope access with the key itself.
- lemlist's REST API allows 20 requests per 2 seconds per API key.

Sources: developer.lemlist.com/mcp/setup, developer.lemlist.com API rate-limits page, lemlist help center MCP setup article.


## Reliability
- CI: not applicable, this is a third-party project we do not control.
- Pinned at mcp-remote 0.8.2 Newer upstream available: mcp-remote 0.14.3; the pin stays at mcp-remote 0.8.2 until it is re-verified.
- Verified 2026-10-02
- We run this server in production, pinned at the exact version, with the install command derived mechanically from that pin so it can be re-verified against the published package.

## Related
- Also in outreach: [Hunter MCP](https://scalably.io/mcp/hunter-mcp)
- Read more: [Claude Code MCP: how to add an MCP server](https://scalably.io/blog/claude-code-mcp), [What is an MCP server? A clear explainer for developers](https://scalably.io/blog/what-is-an-mcp-server)