Skip to content

LinkedIn outreach tools with an MCP server (2026): which ones your AI can actually drive

Which LinkedIn outreach tools have an MCP server, on what plan and with what limits, plus three worked examples of driving outreach from Claude or Cursor.

Namanyay Goel · Updated · 10 min read

Why you are searching for this

You already run half your company from Claude, Cursor or Codex. Your code, your docs, your customer notes. Then outbound comes up and you are back to clicking through a web app, pasting names into a CSV, and checking a separate inbox for replies. You want the same client that writes your code to say "here are 30 people who started hiring SDRs this week, here are drafts, which ones do I send," and then to tell you the next morning who wrote back.

This page lists the LinkedIn outreach tools with an MCP server, on what plan, and with what limits, strictly from each vendor's own pages as of September 2026. Then three worked examples, the safety rules, and what an MCP connection still cannot do. Disclosure: I run PumpGTM, which is on the list.

What an MCP server lets you do, in two sentences

An MCP server is an endpoint your AI client (Claude, Cursor, Codex and others) connects to, which hands the client a set of tools it can call on your behalf: search leads, add them to a campaign, draft a message, read replies. Once connected, you type what you want in plain English and the client calls those tools, so your outreach tool becomes something you talk to instead of something you click through.

Which tools have one, and on what terms

ToolMCP serverTerms and limits, from the vendor's pages
PumpGTMYes, mcp.gigacatalyst.comOAuth. Find buyers, draft and send LinkedIn messages, read replies. Pro plan $75 a month as of September 2026
LemlistYes, app.lemlist.com/mcpOAuth 2.1 or API key. 40+ actions. All plans, including the $69 Email plan
HeyReachYes, per-workspace URLFree with any plan ("HeyReach MCP cost? Nothing"). Key under Integrations, connect via mcp-remote
WaalaxyYes, officialAdvanced (EUR 49) or Business (EUR 69) only. Three tools: get lists, get campaigns, add prospects
ExpandiPrivate beta, waitlistDrafts only, a human launches. Active subscription required ($99 per seat)
ApolloYes, mcp.apollo.io/mcpOAuth or API key, 40+ tools, any plan at no extra cost. Free accounts on personal email cannot search or enrich
ClayYes, officialClaude connector, ChatGPT, Codex. 500 free credits on first connect. Plan gating not published
InstantlyYes, mcp.instantly.ai/mcpAPI key, 31 tools, free with subscription. Email only, no LinkedIn
La Growth MachineYes, mcp.lagrowthmachine.comHosted. Write actions require explicit confirmation, read-only mode available
GojiberryYes, "Connect MCP" in accountFind warm leads, write messages, query campaign insights. Pro $99 a month
DripifyNoHelp center search for "mcp" returns nothing. Read-only API only
Sales NavigatorNo official serverThird-party servers use your session cookie or browser automation and fall under the User Agreement's bot and scraping prohibitions

A few notes the table cannot hold.

Lemlist's is the broadest catalog on the list (lead search, enrichment, sequences, launch, analytics) and it is on every plan, so a $69 Email seat gets the full MCP even though LinkedIn steps themselves need the $109 Multichannel plan.

Waalaxy's official server is deliberately small: three tools, list and campaign reads plus adding prospects. A "Copilot" Claude skill works on any plan including free, but the MCP itself needs Advanced or Business.

Expandi's MCP builds lists, drafts campaigns and replies, and analyzes performance, but every send is a human clicking launch. It is in private beta behind a waitlist.

Apollo's is a data server more than an outreach server. LinkedIn steps in Apollo are manual task reminders, not automation, so what you get from Claude is search, enrichment and email sequences. If you are weighing Apollo against Clay as the data layer, the Apollo vs Clay page does that comparison.

Clay's MCP lets admins set per-rep credit limits, which matters because credit burn is Clay's most repeated complaint. Clay does not send on LinkedIn, so it feeds a sender rather than replacing one.

Sales Navigator deserves its own line. There is no official MCP and no self-serve API; the only sanctioned integration path is the SNAP partner program, which "usually responds to your application within 30 days." Third-party MCP servers exist on GitHub and Apify, and they work by taking your session cookie or driving a browser. LinkedIn's User Agreement (section 8.2) forbids "software, devices, scripts, robots or any other means or processes" to scrape the service and "bots or other unauthorized automated methods to access the Services." Connecting one of those servers to your own account is your account at risk, not the tool's.

Plan prices in the table are from each vendor's pricing page as of September 2026: https://www.lemlist.com/pricing, https://www.heyreach.io/pricing, https://www.waalaxy.com/pricing, https://expandi.io/pricing/, https://www.apollo.io/pricing, https://www.clay.com/pricing, https://instantly.ai/pricing, https://lagrowthmachine.com/pricing/, https://gojiberry.ai/ (pricing is on the homepage), https://dripify.com/pricing, and https://business.linkedin.com/sales-solutions/compare-plans.

What to actually do with it: three examples

Here is what a week looks like with an MCP connection in your client. These are PumpGTM examples because that is what I run, but the shape works with any tool in the table that exposes the same three verbs: find, draft, read replies.

Monday: turn a hiring signal into a list. You open Claude and type: find companies that posted an SDR or AE role on Greenhouse, Lever or LinkedIn Jobs in the last 7 days, 50 to 500 employees, in the US, and show me the head of sales at each. The client calls the find-buyers tool, gets back a scored list, and you ask it to drop anyone under 60 of 100. You are left with maybe 40 people, each one with the reason they are on the list (the job posting) attached. That reason is the first line of the message.

Wednesday: draft, review, send. You ask for a connection request for each of the 40, referencing the specific role they posted, under 300 characters, no pitch. The client drafts them. You read them in the chat, fix the three that sound like a template, and say send. The tool schedules them inside its pacing (for PumpGTM that is a profile view on day 0, a like on a relevant post on day 1, the request on day 2), so "send" does not mean 40 requests in one minute. The review step is where the AI-written message rules earn their keep.

Friday: read replies and hand off. You ask: who replied this week, and which replies are a real conversation versus a polite no. The client calls the read-replies tool, sorts them, and you get five threads worth a follow-up and a short note on each. You tell it to draft follow-ups for the five, read them, send. The 32 second version of this loop is in the run a LinkedIn sales team with Claude post.

Safety: keep the approval gate

An MCP connection removes the clicking, not the judgment. Three rules.

Keep the send in your hands. The tools that do this well make it structural: Expandi's MCP drafts only, La Growth Machine's write actions require explicit confirmation and offer a read-only mode, and in PumpGTM the score gate means anyone under 60 of 100 never gets a message regardless of what you ask the client to do. Whatever tool you pick, do not wire the client into a loop that sends without you reading the draft.

Respect the tool's pacing, not the client's. Your AI client will happily queue 200 requests in one message. The outreach tool should refuse. HeyReach auto-freezes near 100 requests a week and 200 actions a day, Waalaxy caps Advanced and Business at 200 invites a week, Lemlist documents about 20 invites a day. If your tool has no published caps, that is a reason to pick a different one. The founders' ranking weighs published pacing heavily.

Scope the credentials. Lemlist and Apollo let you choose OAuth over a raw API key; prefer OAuth so you can revoke one client without rotating everything. Clay lets admins cap credits per rep. PumpGTM uses OAuth at mcp.gigacatalyst.com. HeyReach's per-workspace key is one key per workspace, so treat it like a password.

Honest limits

An MCP server does not make a tool safe on LinkedIn. It moves the same actions from a browser to a chat. Every LinkedIn automation tool on this list, ours included, runs outside LinkedIn's terms.

Read-heavy servers are more common than send-capable ones. Waalaxy's three tools cannot send a message. Expandi's cannot launch. Artisan's connector (email only, not on this list) cannot launch campaigns. Before you buy for the MCP, check that the verb you want is in the tool list.

Plan gating is real. Waalaxy needs its EUR 49 tier. Expandi needs a paid seat and a waitlist spot. Apollo's free personal-email accounts cannot search. Clay's gating is not published.

Instantly is here because people ask, but it is email only. If your AI needs to reach people on LinkedIn, it is a companion to a LinkedIn tool, not a replacement.

Our own limit: PumpGTM launched in September 2026, does LinkedIn and email only, and builds lists from live signals plus your Sales Navigator imports rather than a 200M contact database. If you want your AI to query a giant database, Apollo or Clay is the better server. If you want it to find the 40 people worth this week's requests and handle the replies, that is what ours is for. The setup takes a few minutes at /mcp, and the broader AI SDR field is on the AI SDR tools for startups page.

Questions people ask

What is an MCP server for LinkedIn outreach? It is an endpoint your AI client (Claude, Cursor, Codex) connects to that exposes your outreach tool's actions as callable tools, so you can find leads, draft messages and read replies by typing in plain English instead of clicking through the app.

Which LinkedIn automation tools have an official MCP server? 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.

Does Sales Navigator have an MCP server? No official one, and no self-serve API. Third-party servers rely on your session cookie or browser automation, which LinkedIn's User Agreement prohibits, so they put your own account at risk.

Is it safe to let Claude send LinkedIn messages? Only with a gate. Keep the send step in your hands, use a tool with published pacing caps that it enforces regardless of what the client asks, and prefer OAuth credentials you can revoke per client.

Do I need a paid plan for the MCP connection? It depends on the tool. Lemlist, HeyReach and Instantly include it with any subscription, and Apollo on any plan. Waalaxy needs Advanced or Business. Expandi needs an active subscription plus a beta invite. PumpGTM's is part of the $75 a month Pro plan.

PumpGTM finds the buyers showing intent this week and runs the outreach from your own LinkedIn account. 7 day trial, $75 a month after.

See how PumpGTM finds buyers

Related comparisons