LinkedIn MCP, and what each one does.
LinkedIn MCP servers that work with Claude today are third-party. Some drive a real browser signed into your account, some use LinkedIn’s official API and can only post, and one outreach vendor ships its own. We have an API and webhooks, and no MCP server. We make a competing LinkedIn outreach tool.
Before you start
- An MCP client, such as Claude Desktop or Claude Code, if you want to try any server below
- A decision about which LinkedIn account a server would act as, and whether its owner agrees
- Ten minutes to read each project’s own README before you connect an account to it
The steps
What MCP is
The Model Context Protocol is, in the words of its introduction (read 2026-11-15), an open-source standard for connecting AI applications to external systems: data sources, tools and workflows. An MCP server exposes those to an AI application, and Claude is one of the applications that supports it.
A LinkedIn MCP server is therefore a program that gives an AI application tools that touch LinkedIn: read a profile, search people, send a message. The tools are only as capable as the way the server reaches LinkedIn, which is what separates the options below.
We found no MCP server run by LinkedIn in our searches on 2026-11-15, and every server below is run by someone else.
Servers that drive a browser signed into your account
These act as the account. They read what a logged-in person would see and do what a logged-in person could do.
stickerdaniel/linkedin-mcp-server (README read 2026-11-15) is an open-source server. Its README lists tools for reading profiles, companies, jobs and the feed, searching people and posts, listing and reading inbox threads, sending messages, and sending or accepting connection requests. It works by driving a real browser signed into your account rather than an official API, and keeps the session on your own machine. It describes itself as an independent project for personal use, and its README carries its own warning about account restrictions. Read it before connecting an account.
Linked API MCP (page read 2026-11-15) is a hosted server, described on its page as unofficial. It lists searching people, companies, posts and jobs, reading profiles, the feed and the inbox, messaging, connecting, posting and commenting, and Sales Navigator use. The page says it runs actions through a dedicated cloud browser on an account you own. It states no price.
What both rely on is a session on your LinkedIn account, not a LinkedIn API for this. Ask what happens to that session, and where it is stored, before you connect one.
Servers that use LinkedIn’s official API
These ask LinkedIn for permission through OAuth and can do only what LinkedIn’s API gives them.
LinkedIn’s documentation for Share on LinkedIn (read 2026-11-15) describes the w_member_social permission, which is required to create a post on behalf of the authenticated member, and lists a throttle of 150 requests a day per member. Nothing on that page covers messages or connection requests.
vlpmedialtd/linkedin-mcp (README read 2026-11-15) is an open-source server on that official API. Its tools create, delete, comment on and react to posts, read your own profile and list company pages you administer. Its README says it can’t read the feed, send messages, manage connections or search, because LinkedIn’s public API doesn’t offer them, and that reading post statistics needs a permission LinkedIn restricts to approved partners.
An official-API server is the narrower one. It is a posting tool, not an outreach tool, and it says so itself.
Servers shipped by an outreach tool
HeyReach’s help article How to integrate HeyReach MCP with Clay (read 2026-11-15) says HeyReach has an official MCP server that connects it with Claude, n8n, Clay, Visual Studio Code and Make, and that in Clay it is used from Use AI mode with your own HeyReach API key. The article doesn’t list the server’s tools, so we can’t say what it can do.
This kind of server wraps an outreach tool’s own API. What it can do is whatever that tool’s API can do, with that tool’s limits.
We have not run HeyReach’s MCP server and say nothing here about how well it works.
What a LinkedIn MCP server can and can’t do
It can give Claude a way to look something up or draft and send one message while you watch. That is useful for research on a few profiles, or for posting from a conversation.
It doesn’t change LinkedIn’s limits on the account it acts as. It answers tool calls from an AI application, and none of the pages we read describe a scheduler, working hours, a daily cap or a way to share leads between several accounts. Running a campaign across a team’s accounts, with each person’s limits respected and one inbox for the replies, is what an outreach tool is for.
It also doesn’t make the account yours to hand around. A server acts as the account it is signed into. Each teammate’s account belongs to that teammate.
For a team, ask of any server: whose account is it, who can see its session, and what stops it sending more than that account should.
What we have instead
We have an API and webhooks, and no MCP server. We don’t publish tool definitions for Claude, and MCP is on our later list, not in the first version.
The API, with a key per workspace, can list campaigns, add leads to a campaign or a list, pause and resume a campaign, stop a lead, read a lead with its lists, campaigns, state and tags, replace tags, list conversations that changed since a time and reply as the conversation’s sender. Webhooks send connection.sent, connection.accepted, message.sent, message.replied, message.received, lead.tagged, lead.finished and campaign.finished to your URL.
Any agent that can make HTTP requests can call that API with the key. That is plain HTTP, and not an MCP server. For working examples, see LinkedIn outreach with n8n and Clay to LinkedIn outreach.
Sending still happens from the connected senders, each at its own limits: 15 connection requests a day to start, up to 25, and never more than 100 a week. See how many connection requests an account can send and pricing: $29 a month per sender, $145 for 5, $290 for 10.
If an MCP server matters to your team, tell us. It is a later item, and the order depends on what people ask for.
You know which kinds of LinkedIn MCP server exist, what each relies on and can do, and where an API with webhooks fits instead.
Is there a LinkedIn MCP server for Claude?
Yes, several, all third-party. As read on 2026-11-15, some drive a browser signed into your account, such as stickerdaniel/linkedin-mcp-server and Linked API MCP, and some use LinkedIn’s official API, such as vlpmedialtd/linkedin-mcp, which only posts and reads your own profile. We found no server run by LinkedIn.
What can a LinkedIn MCP server do?
It depends on how it reaches LinkedIn. The browser-driving servers list reading profiles, searching, reading the inbox, messaging and connecting. The official-API server we read creates and manages posts and cannot read the feed, send messages or search, per its README. None adds limits, scheduling or multi-account sharing on its own.
Is there a LinkedIn MCP server from your tool?
No. We have an API and webhooks and no MCP server in the first version. Any agent that can send HTTP requests can use the API with a key. MCP is on our later list.
Which LinkedIn MCP server should I use?
Match the server to the job and read its README first. For posting, the official-API server is the narrow one. For acting as an account, the browser-driving servers rely on a session on that account. For running a campaign across a team’s accounts, use an outreach tool and its API.
Does HeyReach have an MCP server?
HeyReach’s help article, read 2026-11-15, says it has an official MCP server that connects with Claude, n8n, Clay, Visual Studio Code and Make. The article doesn’t list its tools. We make a competing tool and haven’t tested it.