Agentic outreach
The MCP Arms Race, Smartlead, Lemlist, Instantly Shipped
Inside 30 days three cold email vendors shipped MCP servers. Here's the tool-count, destructive-write and client-support audit GTM engineers actually need.
By Luke Henrik9 min read

TL;DR
- Smartlead now advertises 170 MCP actions, Lemlist's help center documents 70 tools with 35 asking for confirmation, and Instantly ships 31 tools with the shortest ChatGPT path in the category.
- Outreach's MCP catalogs 32 to 44 tools depending on the source but gates everything behind the Amplify add-on with no published pricing, making it an enterprise-only option.
- No cold email MCP covers LinkedIn, and LinkedIn publishes no server of its own, so a real agent stack needs a dedicated LinkedIn MCP alongside the email one.
- The confirmation-gated destructive write pattern (Lemlist, Linkedcamp) is the one that scales with open prompts. Full-write servers (Smartlead, Instantly) are faster for scripted workflows and riskier for exploratory ones.
- Pick two or three MCP servers, not one. Email plus LinkedIn plus CRM is the realistic Q4 2026 stack.
On this page
- Why three vendors shipped inside 30 days
- Smartlead, 170 actions, biggest surface, Claude-first
- Lemlist, multichannel claims, 70 real tools, half ask first
- Instantly, native ChatGPT, the smallest catalog
- The honest state of mcp server sales for engagement platforms
- Where this leaves LinkedIn outbound
- The destructive-tool confirmation question GTM engineers should ask
- The practical stack for Q4 2026
Between early October and early November 2026, three of the biggest cold email vendors shipped or hardened their MCP servers inside the same four-week window. Smartlead now advertises 170 actions across campaigns, leads, analytics and inbox on its homepage. Lemlist's official server at app.lemlist.com/mcp landed with OAuth 2.1 and a tool catalog that the company variously calls 40+, 70 and 100 depending on which page you read. Instantly's mcp.instantly.ai/mcp endpoint became the first native ChatGPT path for a cold email platform worth the name.
This is what an mcp server sales arms race looks like. Not a single splashy launch, but a coordinated scramble by email-first vendors to become the default outbound surface an agent reaches for before LinkedIn-native tools do. If your cold email stack now ships MCP and your LinkedIn stack doesn't, you have a multichannel gap that will show up in your agent prompts the first time you try to build an end-to-end workflow.
This post is the audit. Real tool counts from primary sources, destructive-write behaviour, client support breadth and where the stack still breaks when you ask Claude or ChatGPT to actually run outbound.
Why three vendors shipped inside 30 days
The forcing function is that by mid-2026, more than 10,000 MCP servers had reportedly been deployed in production, with the protocol's SDKs downloaded over 97 million times per month. Agents now expect MCP. If your category peers ship and you don't, your product falls out of the prompt.
The second pressure is ChatGPT. Ten major AI agents support custom remote MCP servers with native OAuth 2.1 as of March 2026, including Claude and Claude Desktop, Claude Code, ChatGPT, VS Code with GitHub Copilot, Zed, Kiro, Amazon Q Developer CLI, OpenCode, Docker MCP Toolkit, and Cursor. The buyer pool now reaches well beyond Anthropic power users, and every vendor without a ChatGPT story is quietly being skipped by GTM engineers building in OpenAI's sandbox.
Third, the category is consolidating. As of October 2026, official hosted MCP servers exist for Sliq, Apollo, Amplemarket, lemlist, HeyReach, Clay, HubSpot, Salesforce, Attio, Instantly, ZoomInfo, Outreach, Salesloft, Smartlead, Explorium, Exa and Crustdata. That's effectively every tier-one GTM tool. The window to ship late without a market-share penalty is closed.

Smartlead, 170 actions, biggest surface, Claude-first
Smartlead's homepage now states that teams can use Smartlead MCP to run outbound with 170 actions across campaigns, leads, analytics and inbox. That's up from the 116-tool catalog that launched as the most comprehensive outbound-specific MCP integration available as of April 2026.
The install is a remote SSE server. The install Smartlead's help center documents today is a remote server over SSE, added to Claude Desktop's configuration through the mcp-remote package, with the address https://mcp.smartlead.ai/sse?user_api_key=YOUR_API_KEY. API access starts on the Pro plan.
What the 170 actions actually cover. Campaign management, lead lifecycle, email account configuration, warmup management, deliverability diagnostics via SmartDelivery, analytics and webhook management. Smartlead's SmartDelivery tools are exposed through the MCP server, so Claude can check warmup status, flag accounts with declining health scores, and monitor blacklist status before they compound into domain reputation damage. That diagnostic surface is where Smartlead genuinely leads the category.
The gap. ChatGPT is still awkward. It is not a native ChatGPT connector as of August 2026, though technical users may be able to add it through ChatGPT's Developer Mode. And there are no native LinkedIn actions on Smartlead's side at all, which matters for anyone running a real multichannel sequence.
Lemlist, multichannel claims, 70 real tools, half ask first
Lemlist shipped the server with the most interesting destructive-write model. Lemlist runs an official remote MCP server at app.lemlist.com/mcp, included on every plan, which connects with OAuth or an API key. Its help center lists 70 tools across campaigns, leads, enrichment, CRM, inbox, analytics, deliverability and account settings, and half of them ask for confirmation before running.
That 35-out-of-70 confirmation count is the right pattern. The write tools include sending messages, deleting leads, purchasing domains and provisioning mailboxes, which is exactly the surface where an agent hallucination will cost you money or reputation.
Client support is broad. It supports Claude on web, desktop and Cowork, Claude Code, Cursor, ChatGPT and the Codex CLI and IDE extension, with OAuth as the recommended authentication method.
The practical catch is pricing. The MCP server is included on all plans. LinkedIn automation is not. LinkedIn sits behind the $109/user/month Multichannel tier, which means the "multichannel MCP" story only applies if you're already paying for the top plan on every seat.
The documentation gap worth knowing. How many tools it has depends on the page. 40+ on the product page, around 100 in one lemlist blog post, and 70 in the help center's full tool reference. For a GTM engineer trying to scope a build, that's a planning problem.
Instantly, native ChatGPT, the smallest catalog
Instantly's move was strategic rather than quantitative. Instantly runs an official hosted MCP server at mcp.instantly.ai/mcp that you add as a custom connector. It's free with your Instantly subscription, authenticates with your API key, and exposes 31 tools across campaigns, leads, emails, analytics, and sending accounts.
Thirty-one tools is a fraction of Smartlead's catalog, but Instantly spent the engineering budget on reach. In ChatGPT, open Settings → Security and login, enable Developer Mode, and create a connector pointed at https://mcp.instantly.ai/mcp with your API key in the Authorization header. That is the shortest path from ChatGPT to a live cold email campaign that exists today.
The tradeoff is that smaller catalogs leave reasoning gaps. An agent working with 31 tools will reach for the Instantly tool for lead operations and bounce out to a webhook or a CRM MCP for anything unusual. That's fine for a scripted workflow, less fine for the kind of open-ended "audit my sending and fix what's broken" prompt that justifies MCP in the first place.
The honest state of mcp server sales for engagement platforms
For the enterprise segment the reference point is Outreach. Outreach has a listing in Anthropic's Connectors Directory dated February 2026, and that listing registers 15 tools, while its documentation describes 32 and Outreach's MCP server exposes around 44 tools spanning conversation intelligence, sequences, prospects, accounts, opportunities and configuration, which is the deepest catalog of any sales engagement MCP server we have reviewed.
The gate is Amplify. As of September 2026, Outreach's pricing page carries no dollar figures at all. As of September 2026 its pricing page lists four Amplify tiers differentiated only by AI-credit allocation, Essentials at 10,000 credits, Core at 25,000, Plus at 50,000 and Pro at 100,000, each marked Request pricing. For most agencies and mid-market teams, Outreach MCP is not actually available, it's an enterprise upsell.
Outreach MCP has no update tools at all. Outreach made that an explicit product decision. That's the opposite of Lemlist's half-destructive catalog and it reflects an enterprise bet that agents should propose changes a human applies, not change records directly.
Where this leaves LinkedIn outbound
Here is the gap Smartlead, Instantly and Outreach cannot close. LinkedIn's official API prohibits automated outreach and LinkedIn publishes no MCP server. If your agent needs to touch LinkedIn, it has to touch it through a third-party automation platform's MCP.
The set of options is small. As of September 2026. PumpGTM, Lemlist (all plans), HeyReach (free), Waalaxy (Advanced or Business), La Growth Machine, Gojiberry, plus Apollo, Clay and Instantly for data and email. Expandi's is a private beta that drafts only. Dripify has none.
This is where Linkedcamp's MCP fits. Every plan ships a 133-tool server covering 64 read-only tools and 28 destructive tools that ask for confirmation first, with the rest being lower-risk writes. The destructive-confirmation pattern matches Lemlist's approach, the catalog depth sits between Instantly and Smartlead, and the client support matrix covers Claude, Claude Code, Cursor, Windsurf, Zed and other MCP clients, plus ChatGPT through the same Developer Mode path Instantly uses. Full detail lives on the MCP page.
The piece that only matters to agencies. The Linkedcamp agency owner key reaches every connected client sub-account through the same server. Smartlead, Lemlist and Instantly all assume a single workspace per key, so agencies running the MCP against five or fifty clients have to rotate keys. That's a solved problem for CRM pulls, a real problem when the agent is driving actual sends.
If you're assembling a stack right now, the pattern that works is one email MCP (Smartlead or Instantly depending on whether you need the deliverability depth or the ChatGPT reach), one LinkedIn MCP, and one CRM MCP (HubSpot or Pipedrive). The LinkedIn-first sequence data argues strongly for keeping LinkedIn as the first touch, which makes the LinkedIn MCP the one you actually need to pick carefully.

The destructive-tool confirmation question GTM engineers should ask
Three patterns are now visible in the sales MCP market, and they matter more than tool counts.
- Confirmation-gated writes. Lemlist's 35-of-70 and Linkedcamp's 28 destructive tools that ask first. The agent can run, but a human approves the destructive step. This is the pattern that scales with a Claude or ChatGPT Developer Mode prompt that might misread intent.
- No writes at all. Outreach's "no update tools" stance. Safest, least useful for day-to-day execution. Works if your agent is a briefing tool, not an operator.
- Full writes, no gating. Smartlead and Instantly largely sit here. Fast for scripted workflows, risky for open prompts. Because these actions can modify live data or initiate outreach, companies should require confirmations for sensitive operations.
The second question worth asking is whether the server is tools-only or exposes resources and prompts too. Outreach has not exposed any resources or prompts, so the server is tools-only. Every platform we audited is in the same spot. Resources and prompts are where MCP goes next, and no outbound vendor has shipped them yet.
The third question is schema stability. MCP tool schemas change when Outreach updates the hosted server, and Outreach says outright that it is continuously adding tools and that you should refresh periodically. If you're building production agents, every one of these servers will move under you. Plan for refreshes.
The practical stack for Q4 2026
For a GTM engineer or agency ops lead shipping this quarter.
- Deliverability-heavy outbound with existing Smartlead. Smartlead MCP for the diagnostic surface, accept the Claude-only reality.
- ChatGPT-first team. Instantly MCP for the native path, accept the 31-tool ceiling.
- Multichannel with budget. Lemlist at the Multichannel tier, accept the per-seat pricing math.
- Agency running multiple clients on LinkedIn. Linkedcamp MCP for the agency-owner key that reaches every sub-account, paired with whichever email MCP you already run. See the agency pricing math for when per-seat tools stop working.
- Enterprise on Outreach with Amplify. You already know. The server is there, writes are limited, Amplify credits are the real cost.
The arms race will continue. Expect Lemlist to clarify its tool count by year-end, Smartlead to add native ChatGPT, and at least one more LinkedIn-native vendor to ship MCP in Q1 2027. The question isn't whether to add an MCP layer to your outbound stack. It's which two or three servers you pick and how you split destructive writes between them.


