LinkedIn MCP server
Quick answer
LinkedIn does not publish an MCP server. Every LinkedIn MCP you will find is built by someone else, in one of three ways: it drives a logged-in browser session, it wraps LinkedIn's official API, or it comes with an outreach tool that already manages LinkedIn accounts. We run our LinkedIn outreach from Claude through the third kind, HeyReach's server, since August 2026.
- Published by
- No official server from LinkedIn. We use HeyReach's official MCP server
- How it runs
- Hosted by HeyReach, connects with your HeyReach MCP key
- Get it
- www.heyreach.io/mcp
What your assistant can do with it
- Browser-session servers: read profiles and messages and act as your account, by automating a logged-in LinkedIn session
- Official-API servers: work with your own profile, posts and company page within what the API allows
- Outreach-tool servers (ours: HeyReach): run campaigns, sequences and lists across several sender accounts, read replies and stop leads
How to connect it
- Decide what you need first: posting and analytics for your own profile, or outreach to prospects.
- For outreach, connect the MCP server of the outreach tool that manages your sender accounts, with its own key.
- Test with a real read (a campaign, a conversation), not just the tool list.
- Keep account limits, like daily invitations, in the outreach tool's interface.
How we use it
Our LinkedIn outreach runs on HeyReach, and Claude drives it through HeyReach's MCP server: it reads campaign stats, pulls the conversations that need a human, stops leads who replied elsewhere and sets up new campaigns and lists. We never let an assistant drive a LinkedIn browser session directly: the sender accounts are what we protect first.
Where it breaks
- Browser-session servers act as your account through automation, which LinkedIn's User Agreement prohibits. The account at risk is the one you connect.
- Official-API servers only see what the API gives: mostly your own profile, posts and pages, not prospecting data.
- Through an outreach tool, you get what the tool exposes. With HeyReach, the daily invitation limit of an account and the review of a sequence stay in the interface.
- The copy uses the variables you load with each lead, not the name and company read from the profile. Load them clean.
Our take. There is no LinkedIn MCP from LinkedIn, so pick by risk. For outreach, go through a tool that already manages accounts and limits; that is what we run. For your own posts and analytics, an official-API server is the safe route.
Frequently asked questions
Is there an official LinkedIn MCP server?
No. LinkedIn does not publish one. The servers available are built by third parties, and the largest community projects say they are not affiliated with LinkedIn.
Is a LinkedIn MCP server safe for my account?
It depends on how it works. Servers that automate a logged-in browser session act against LinkedIn's terms and put the connected account at risk. Servers on the official API, or from an outreach tool that manages limits, are the safer routes.
Which LinkedIn MCP do you use?
HeyReach's official MCP server, because our outreach already runs on HeyReach. Our HeyReach MCP page covers what it can do and the traps we hit.
More servers we run: MCP servers for GTM.
Want this wired into your stack
We build and run GTM systems where Claude works across your CRM, data and sending tools, with rules it has to follow.
Book a GTM audit