IonBin
All pages
Search

lemlist

Sales outreach
Sales MCPAPI/CLIFile import

Independent review. Unpaid; no partnership with lemlist. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.

Outreach platform for email and LinkedIn sequences. Its MCP server lets AI tools audit campaigns, create or update sequences and manage leads, over OAuth or an API key; a public API is also documented.

The Ion perspective

The five-point review

Judgment, not a score. Documentation checked 2026-10-18.

Value
Outreach platform for email and LinkedIn sequences. Its MCP server lets AI tools audit campaigns, create or update sequences and manage leads, over OAuth or an API key; a public API is also documented.
Differentiation
Documented fit: Personalized multichannel sequences. Uniqueness is not established.
Replaceability and switching
Compare Instantly. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Teams that need a full CRM. Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.

Connections: MCP connections · APIs · Portability and vendor lock-in.

Best for
  • Personalized multichannel sequences
Not for
  • Teams that need a full CRM

Top use cases

  • Automate sequences and lead updates through the API source ↗
  • Audit campaigns, update sequences and manage leads from an AI tool source ↗

In depth

Plans

Email is $55/month billed yearly or $69 monthly for unlimited users and 50,000 emails/month. Multichannel starts at $87/user/month yearly or $109 monthly, adding LinkedIn, SMS and calling; WhatsApp is an add-on. MCP/CLI are included. Data enrichment starts at $16/month yearly or $20 monthly. Confirm billing currency and team quote at checkout. Checked 2026-10-18. source ↗

Connect and verify before sending

The hosted MCP supports OAuth or an API key and documents Claude, Cursor, ChatGPT and Codex. Access depends on your lemlist team and client controls. Begin with a read-only campaign audit, then review target leads, exclusions and sequence edits before launching. Use each client's current documentation for setup details. source ↗

How to use it with AI

How lemlist connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.

PlatformMCP / connectorAPI (agent-written code)BrowserUpload / export
Claude (incl. Claude Code) Not documented Setup steps in lemlist's help center. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. lemlist named integration docs ↗Claude (incl. Claude Code) MCP docs ↗ Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands lemlist publishes an API, but this pairing still needs network, authentication and execution-scope checks. lemlist API ↗Claude (incl. Claude Code) docs ↗ Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). lemlist is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. lemlist's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. lemlist file docs ↗Claude (incl. Claude Code) file docs ↗
OpenAI Codex Not documented Setup steps in lemlist's help center. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. lemlist named integration docs ↗OpenAI Codex MCP docs ↗ Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces lemlist publishes an API, but this pairing still needs network, authentication and execution-scope checks. lemlist API ↗OpenAI Codex docs ↗ Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. lemlist is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. lemlist's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. lemlist file docs ↗OpenAI Codex file docs ↗
Google Antigravity Not documented lemlist has an official MCP server and Google Antigravity supports MCP, but lemlist's docs don't name this pairing. Auth setup may differ. lemlist MCP docs ↗Google Antigravity MCP docs ↗ Not documented Google Antigravity: Agents edit code and run tasks lemlist publishes an API, but this pairing still needs network, authentication and execution-scope checks. lemlist API ↗Google Antigravity docs ↗ Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. lemlist is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. lemlist's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. lemlist file docs ↗Google Antigravity file docs ↗

lemlist's docs also name: ChatGPT.

Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.

Agent compatibility

MCPAPI/CLIFile import
LevelStatusDetail / source
Native connector / MCPYes Official docs ↗
API / CLIYes Official docs ↗
Browser / manualNo Browser access is recorded alongside a documented programmatic route.
File upload / importYes Official docs ↗

Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.

Appears in these proposed stacks

Connection capabilities to compare

An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.

Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.

Workflows using this tool

Review

No long-form review yet. Verdict is based on research, not hands-on testing.

Alternatives

Instantly

Sales outreach

Cold email platform for sending sequences at scale, with deliverability tools. Its MCP server lets an AI assistant create campaigns, add leads, pull analytics and pause campaigns.

MCPAPI/CLIFile import
Sales