The short answer
A LinkedIn MCP server connects Claude, ChatGPT or another assistant to LinkedIn. LinkedIn does not publish one you can use.
LinkedIn's developer homepage still shows a "Develop with MCP" link with a New label (rechecked 22 October 2026). It leads to a developer login, with no documentation, announcement or public endpoint.
Your real options are third-party: open-source browser-session servers, open-source servers on your own API app, or hosted connectors from posting tools.
LinkedIn's API Terms (section 3.1) bar using the APIs "to automate posting", and member sign-ins last 60 days. Keep a human approval on every post.
Install trap: the popular repository linkedin-mcp-server publishes as mcp-server-linkedin. The package named linkedin-mcp-server is an unrelated one-release project.
Microsoft's catalogue of official MCP servers does not mention LinkedIn.
Updated 22 October 2026. We rechecked LinkedIn’s developer site: the Develop with MCP link is still there and still undocumented. New first half on what a LinkedIn MCP server is, the options for Claude and ChatGPT, and the posting rules; package and repository figures refreshed.
A LinkedIn MCP server is a connector that lets an AI assistant such as Claude or ChatGPT read from or post to LinkedIn. LinkedIn does not publish one: its developer homepage shows a “Develop with MCP” link that leads to a developer login, with no documentation behind it. Every LinkedIn MCP server you can use today is third-party, either an open-source server you run yourself or a hosted connector from a posting tool.
What is a LinkedIn MCP server?
MCP, the Model Context Protocol, is the open standard assistants use to call outside tools. A LinkedIn MCP server exposes tools such as “create post” or “get my posts” and holds your LinkedIn sign-in. The assistant decides when to call a tool; the server decides which tools exist and how it reaches LinkedIn.
Through LinkedIn’s official API: you sign in with OAuth, and posting runs through LinkedIn’s sharing permission. This is the route hosted posting tools use.
Through a browser session: the server drives a logged-in LinkedIn page. It can read far more, but it is the route LinkedIn’s User Agreement prohibits.
Your options for a LinkedIn MCP server
The three kinds of LinkedIn MCP server, checked 22 October 2026.
Type | How it signs in | Can it post? | Main risk or limit |
|---|---|---|---|
Open-source, browser-session (for example stickerdaniel/linkedin-mcp-server) | Your session in a real browser | Depends on the project | Its own README warns that automated access breaks LinkedIn’s User Agreement and can get accounts restricted |
Open-source, official API | OAuth with your own LinkedIn developer app | Yes, with the sharing permission | You set up and maintain the app; sign-ins expire after 60 days |
Hosted connector from a posting tool | OAuth through the tool | Yes, usually with an approval step | Sign-ins expire after 60 days; you trust the tool with your token |
Free LinkedIn MCP servers: the open-source ones cost nothing but your time and, for the browser kind, your account risk.
LinkedIn MCP server on GitHub: the best-known project, stickerdaniel/linkedin-mcp-server, had about 4,000 stars on 22 October 2026. Read the package section below before installing it.
Comparing hosted connectors: nearly all of them cover LinkedIn and Twitter, so channel coverage is not the difference. What actually differs between social MCP connectors covers the rest.
LinkedIn MCP server for Claude
A hosted connector gives you a server URL. In Claude you add it as a custom connector, sign in to LinkedIn through the tool, and switch it on in a chat. Local open-source servers work only in Claude Desktop or Claude Code on that computer, not on claude.ai or your phone. The full walkthrough, with the permissions to set before the first post, is in connect Claude to LinkedIn and Twitter.
LinkedIn MCP server for ChatGPT
OpenAI’s help center says full custom MCP connectors, including write actions such as posting, are for ChatGPT Business, Enterprise and Edu workspaces. On personal plans the route is usually a listed app or an automation tool. Every route is compared in can ChatGPT post to LinkedIn and Twitter.
Using a LinkedIn MCP server for posting: the rules
No automated posting: LinkedIn’s API Terms, section 3.1, bar using the APIs “to automate posting on the LinkedIn Services”. Keep a human approval on every post the assistant drafts.
60-day sign-ins: LinkedIn member sign-ins last 60 days, so every API-based connector asks you to reconnect. Which servers handle that well is in which LinkedIn MCP servers stop working after 60 days.
Account risk: what the terms say and what can and cannot be known is in will a LinkedIn MCP get your account restricted.
[ from the team behind this blog ]
Post on LinkedIn and Twitter in a way that reads like you
VoiceMoat is the Personal Brand OS for LinkedIn and Twitter. audenAI, the brain inside it, learns from your own posts, then helps you create, schedule and grow.
Creator plan $35 a month after the trial. Cancel anytime.
Does LinkedIn have an official MCP server?
Not one you can use. On 22 October 2026 LinkedIn’s developer homepage still showed “Develop with MCP” twice: in the Docs and tools menu with a New label, and as a main button beside Create app. Both point to linkedin.com/developers/apps/develop-with-mcp, which shows nothing without a developer login. There is still no documentation, no announcement and no public endpoint.
What is there and what is not. Rows marked September are from our 9 September check and were not repeated.
Checked | Result |
|---|---|
LinkedIn’s developer homepage (22 October) | “Develop with MCP” in the menu with a New label, and as a main call to action |
The link’s destination (22 October) | A developer page that renders nothing without a login |
Microsoft’s public catalogue of official MCP servers (22 October) | No mention of LinkedIn |
LinkedIn’s product catalogue and developer documentation (September) | No MCP product or page |
The official MCP registry (September) | Many LinkedIn servers, none under a LinkedIn or Microsoft namespace |
The obvious MCP hostname (September) | Resolved only as an alias to LinkedIn’s content delivery network; every path returned 404 |
Archived captures date the link’s arrival. The phrase does not appear on the homepage in captures from June or early July 2026, and does appear in captures from early August. In September the developer console also carried feature flags named for configuring MCP and generating MCP tokens, which suggests a service LinkedIn operates rather than a tutorial. If you hold a LinkedIn developer account, you can open the page yourself.
The install that gets you the wrong package
The best-known community project’s repository is named linkedin-mcp-server, and articles correctly call it that. It publishes its package under the same three words in a different order.
Two packages, checked at the Python package index on 22 October 2026.
Package name | Releases | Points to |
|---|---|---|
mcp-server-linkedin | 26, latest 4.27.0 (10 October 2026) | The well-known project, about 4,000 stars |
linkedin-mcp-server | 1, version 1.0.0 (January 2026) | An unrelated, much smaller repository |
So you read the project name, type the matching install command, and get somebody else’s single-release package, which then asks for LinkedIn access because that is what servers in this category do. It is a naming collision, not a deception: the smaller project says plainly that it is a community project not endorsed by LinkedIn.
Where the warning label falls off
The well-known project is careful about what it is. Its README says it is an independent open-source project, not affiliated with LinkedIn or Microsoft, and warns that accounts using automated tools can be restricted or banned. In September we found the same project repackaged in a container catalogue under the plain title LinkedIn, with no disclaimer and still wanting a session cookie. Be wary of any listing that promises no account risk: no third party can promise that.
How to check any LinkedIn MCP server yourself
Check the namespace, not the name. In the official registry the publisher prefix is the one field an author cannot write for themselves.
Check the package, not the repository. Confirm the package page links to the repository you meant. Word order matters.
Count the releases. One release on one date is a different proposition from dozens across a year.
Look for the disclaimer. Honest projects say plainly that they are not affiliated with LinkedIn.
Check the vendor’s own site. That is how we found the Develop with MCP link, and it took one page load.
Why LinkedIn has kept it quiet
Not because LinkedIn is behind on AI: it ships AI features across its products, and Microsoft maintains a public catalogue of official MCP servers for Azure, GitHub, Teams, Word and more, without LinkedIn in it. On the Twitter side, the API team publishes an open-source server, xmcp.
The likelier explanation is policy. LinkedIn opens bounded API surfaces and closes open-ended ones, and a general-purpose server where an assistant asks for whatever it decides it needs is close to the shape being closed. That may be why whatever sits behind the link is arriving quietly and gated.
What LinkedIn’s API offers today
Self-serve: sign-in, sharing on a member’s behalf, verifications, events and page plugins. This is where a posting integration lives.
Application-gated: advertising, community management and data integrations. The developer homepage now also shows a Company Intelligence API with an “Apply now” button.
Closed: reading a member’s own post content and full profile access.
Member data portability: self-serve, but only for members in the European Economic Area and Switzerland.
The analytics side has a similar shape, covered in does LinkedIn have an analytics API.
Where we sit
We publish a VoiceMoat MCP connector that connects LinkedIn and Twitter to Claude, ChatGPT and Grok. It is not official and not endorsed by LinkedIn. It signs in over OAuth rather than a session cookie, posts through LinkedIn’s API, and expires every 60 days like every connector on that route. If you want no credential at all, our Claude skills are plain files that cannot reach LinkedIn.
If whatever sits behind Develop with MCP turns out to be a real hosted server with sanctioned access, that is good news for everyone, including us, and we will update this page.
Frequently asked questions
Is there an official LinkedIn MCP server?
Not one you can use. LinkedIn's developer homepage shows a "Develop with MCP" link with a New label, rechecked on 22 October 2026, but it leads to a developer login and there is no documentation, announcement or public endpoint. Every LinkedIn MCP server in use today is third-party.
How do I add a LinkedIn MCP server to Claude?
Get the server URL from a hosted connector, add it in Claude as a custom connector, sign in to LinkedIn through the tool and switch it on in a chat. Local open-source servers work only in Claude Desktop or Claude Code on that computer. Set posting tools to need your approval first.
Can I use a LinkedIn MCP server with ChatGPT?
OpenAI's help center says full custom MCP connectors with write actions, such as posting, are for ChatGPT Business, Enterprise and Edu workspaces. On personal plans the usual routes are a listed app or an automation tool.
Is there a free LinkedIn MCP server?
Yes, open-source ones on GitHub. The best-known, stickerdaniel/linkedin-mcp-server, drives a real browser session, and its own README warns that automated access breaks LinkedIn's User Agreement and can get accounts restricted.
Can a LinkedIn MCP server post for me automatically?
It can post through LinkedIn's API, but LinkedIn's API Terms, section 3.1, bar using the APIs to automate posting. Keep a human approval on each post. LinkedIn member sign-ins also expire after 60 days, so you will need to reconnect.
Why did my LinkedIn MCP install give me the wrong package?
Probably a name collision. The best-known repository is named linkedin-mcp-server but publishes its package as mcp-server-linkedin. A package called linkedin-mcp-server exists and is an unrelated one-release project. Check that the package page links to the repository you meant.
AI disclosure
Written and fact-checked by Prateek Singh. VoiceMoat publishes an unofficial LinkedIn MCP connector and is one of the third parties this article describes. The Develop with MCP link was opened and confirmed on LinkedIn's live developer homepage on 9 September 2026; the page behind it requires a developer login and its contents are explicitly not reported here. The date it appeared comes from archived captures of that homepage. The package collision was verified directly at the package index rather than from a secondary source. Absences were checked against LinkedIn's product catalogue, its developer documentation, its developer news, the official MCP registry, both GitHub organisations and Microsoft's own catalogue of official MCP servers, and are reported with those places named. An earlier version of this article stated flatly that no official MCP server existed; it was corrected before publication when that check was run. Facts rechecked and keyword re-targeted on 22 October 2026.
Keep reading
Industry
Can Claude post to Twitter? Yes, and here is the bill
Twitter publishes three official MCP servers, and the one everybody installs cannot create a post. You can prove that from its OAuth scopes, which do not include write access to posts at all. Meanwhile every guide prices this as fifteen thousandths of a dollar per post, which is the sticker price and not the bill. A realistic assistant session costs two to eighteen times that, and the difference is mostly links.
13 min read
·
Industry
Can Claude post to LinkedIn? Yes, and LinkedIn's own developer terms say it should not
Claude can publish to LinkedIn through a connector, using a permission LinkedIn hands out self-serve. The final item in LinkedIn's API Terms of Use is a flat ban on using the APIs to automate posting. Every guide we read cites the wrong document, and several sell scheduling while calling themselves the compliant option. Here is the clause, what Claude can and cannot actually publish, and why the connector most people recommend cannot work on claude.ai at all.
12 min read
·
Industry
Which LinkedIn MCP servers stop working after 60 days
Every comparison of LinkedIn MCP servers sorts them by stars, tools and terms risk. None of them mentions that the ones using LinkedIn's sanctioned login die after 60 days and cannot renew themselves. We went through the field server by server. Only a handful use that route at all, most of those are abandoned, and the ones that never expire avoid the problem by holding a credential that lasts a year and cannot be revoked individually.
9 min read
·
Industry
X API pricing in 2026: what it actually costs
The X API is pay-per-use: $0.015 a post, $0.200 with a link and $0.005 a read, rechecked 22 October 2026. What decides your bill is what the rate card leaves out: billable events are not calls, images count as extra posts, endpoint choice changes read costs five-fold, and the read cap moved three times. Plus what the API returns when the money runs out, which we measured because it happened to us.
20 min read
·
Industry
Does LinkedIn have an analytics API? Yes, and almost no guide mentions it
The settled wisdom is that LinkedIn gives you no way to read your own post performance programmatically. That stopped being true on 8 July 2025, when LinkedIn shipped a member post analytics endpoint with eleven metrics. We read seventeen pages that rank for this question and only three name it. Here is what exists, who can actually get it, the metrics LinkedIn will not give a personal profile at all, and the storage question LinkedIn has never answered.
14 min read
·
From the Twitter algorithm series
The Twitter/X algorithm in May 2026: why voice wins under the new transformer
Read ›
