TL;DR
– No official LinkedIn MCP exists: LinkedIn does not publish one, its API only covers posts and pages, and its terms ban scraping.
– Community LinkedIn MCP servers mostly scrape the platform, which risks your account.
– Clay finds and enriches contacts, Derrick sources and enriches from LinkedIn, and La Growth Machine runs multichannel outreach with native sending.
– Source and enrich with Clay or Derrick, then launch outreach in La Growth Machine, all from one assistant.
There is no official LinkedIn MCP server. LinkedIn does not publish one, and its API and terms of service do not allow profile search, scraping, or messaging through third-party tools. A few community “LinkedIn MCP” servers exist, but most of them scrape LinkedIn, which puts your account at risk.
What people actually want from a “LinkedIn MCP” is to prospect on LinkedIn from an assistant: find profiles, enrich them, and reach out. That is better served by MCP servers built for go-to-market work: Clay, Derrick, and La Growth Machine.
New to the protocol? Start with what an MCP server is.
Is there an official LinkedIn MCP?
No. LinkedIn has not released an MCP server, and it has no official Claude connector (yet).
Its public API is limited to publishing and company-page actions, not the prospecting most people are after. And its terms of service prohibit unauthorized scraping or automation of the platform.
You will find community LinkedIn MCP servers on GitHub and MCP directories. Treat them with caution.
⚠️ Most community LinkedIn MCP servers scrape LinkedIn or drive a logged-in session. That breaches LinkedIn’s terms and can get your account restricted or banned. The few that use LinkedIn’s official API only reach posts and pages, not profile search or outreach.
What people actually want from a “LinkedIn MCP”
The intent behind the search is rarely “an MCP for its own sake.” It is prospecting work people want to run from an assistant:
- find and search LinkedIn profiles that match an ICP
- enrich those profiles with a verified email or phone
- build a clean target list
- send connection requests and messages
- manage replies in one place
None of this needs a LinkedIn MCP specifically. It needs MCP servers built for sourcing, enrichment and outreach.
The MCP servers that cover these use cases
Three MCP servers, used together, cover the full LinkedIn prospecting motion from an assistant like Claude or ChatGPT (OpenAI).
Clay MCP
What it does
Clay is available as an official connector for Claude and ChatGPT. From the assistant you can search Clay’s contact database, pull detailed contact info, and check interaction history, then push records to your CRM.
⚠️ The Clay MCP is read-focused. You cannot trigger Clay’s 100+ provider enrichment waterfall from the assistant, that still runs in Clay’s UI. See the Clay MCP.
Derrick MCP
What it does
Derrick is a sourcing and enrichment MCP that works on LinkedIn data. From the assistant it can search LinkedIn profiles, find leads inside target companies, return a verified email and phone, and push the result straight into La Growth Machine.
It is a good fit when the starting point is a LinkedIn profile or a company and you want a contactable lead out of it.
La Growth Machine MCP
What it does
La Growth Machine is an outreach platform that connects multichannel campaign execution to proven revenue impact, and it ships its own MCP server. From the assistant you can build an audience, including from a LinkedIn or Sales Navigator search URL, launch a LinkedIn and email sequence, and handle the inbox.
This is also the safest way to act on LinkedIn. La Growth Machine sends through native LinkedIn rates rather than a browser extension that simulates activity, which keeps account risk low. See the La Growth Machine MCP.
A LinkedIn prospecting use case, end to end
Here is the loop a RevOps or GTM engineer can run from one assistant, with no LinkedIn MCP involved.
- Source target profiles from a company or an ICP with Derrick, or search contacts in Clay.
- Enrich each one with a verified email and phone.
- Launch a LinkedIn and email sequence in La Growth Machine, built from that list.
- Reply to the leads who answer, in the same assistant.
The data MCPs (Clay, Derrick) supply clean, contactable leads. La Growth Machine runs the outreach and logs the activity. The assistant orchestrates between them.
A word on LinkedIn’s terms and account safety
LinkedIn actively limits scraping and automation that it has not authorized.
- Avoid community MCP servers that scrape profiles or drive your logged-in session.
- Prefer official data providers (Clay, Derrick) and native sending (La Growth Machine).
- Treat any tool that promises “unlimited LinkedIn automation” as a ban risk.
The goal is a prospecting motion that lasts, not one that gets your account flagged.
Frequently asked questions
Is there an official MCP server for LinkedIn? No. LinkedIn does not publish an MCP server. Community servers exist, but most scrape the platform and breach its terms of service.
Does LinkedIn have a Claude MCP or connector? No official one. For LinkedIn prospecting data inside Claude, Clay is available as a connector, and Derrick exposes LinkedIn sourcing and enrichment over MCP.
How can I prospect on LinkedIn with an assistant? Use Clay or Derrick to source and enrich leads, then La Growth Machine to launch a LinkedIn and email sequence, all from the assistant.
Are community LinkedIn MCP servers safe to use? Usually not. Scraping or automating a logged-in session breaches LinkedIn’s terms and risks account restrictions. Prefer official providers and native sending.
What is the safest way to send LinkedIn messages from an assistant? La Growth Machine, because it sends through native LinkedIn rates rather than a browser extension that simulates activity.