LinkedIn MCP Servers in 2026: What They Are, and 13 Compared

A LinkedIn MCP server is a connector that lets an AI app such as Claude, ChatGPT or Cursor act on LinkedIn for you: publish and schedule posts, or read profiles and messages, depending on the server. LinkedIn has no official MCP server, and neither Anthropic nor OpenAI ships a LinkedIn connector, so every one you can install is third-party. What separates them is how they reach LinkedIn: official-API servers post with a permission you grant on LinkedIn's own sign-in screen (OAuth), while scraping servers drive a browser logged in as you, which LinkedIn's User Agreement prohibits and which can get an account restricted.

This page sorts the thirteen that come up most, using two sources only: each vendor's own documentation, and LinkedIn's own API documentation on Microsoft Learn. The original twelve were checked on 26 September 2026 and Postiv on 21 October 2026, and every row links to where the fact came from. For servers that post to every network, not just LinkedIn, see social media MCP servers compared.

Short answer: publish, or read?

To publish and schedule LinkedIn posts from Claude, ChatGPT or Cursor, use a hosted server that signs you in with LinkedIn through its own approved app, so there is no developer app and no token to manage. Antwork is free for 2 connected accounts and also posts to twelve other networks from the same connection; Postiv is a paid LinkedIn suite with branded visuals and approvals. Kalovio, 2pr.io, Taplio and PostMCP are in the same group.

To read profiles, search people, read your inbox or send connection requests, the servers that can do it drive a logged-in browser (stickerdaniel/linkedin-mcp-server, Linked API) or scrape public pages (Apify), because LinkedIn's API keeps those jobs for approved partners. None of them publishes posts.

Official API vs scraping

The one question to ask of any LinkedIn MCP server is how it connects. It decides what the server can do, and what it risks.

If all you want is to publish, an official-API server does the whole job and carries none of the scraping risk. Reach for browser automation only for reading and outreach, which the open API does not offer.

The three kinds of LinkedIn MCP server

Every server below is one of three kinds, and the kind decides what it can do and what it risks:

1. Hosted, on LinkedIn's official API. You sign in with LinkedIn once (OAuth) and the server posts through the API, and some also comment and react. No developer app, no token to paste, nothing to install. Built for publishing; it cannot send DMs or connection requests, because LinkedIn reserves those for approved partners. Antwork, Postiv, Kalovio, 2pr.io, Taplio and PostMCP.
2. Automation bridges. LinkedIn is one connector among hundreds, used as a step in a wider workflow. Composio and Zapier.
3. Browser automation, usually open source on GitHub. The server drives your logged-in LinkedIn session, so it can read profiles, search people and send messages, and it falls under LinkedIn's rules on automated access. stickerdaniel/linkedin-mcp-server and Linked API.

What LinkedIn's API lets any MCP server do

Before comparing tools, it helps to know what LinkedIn's official API allows. That list decides which MCP servers can be built "properly" and which can only work by automating a browser. This is the part other comparisons skip, and it answers most of the "why can't my AI do X on LinkedIn" questions.

Three practical consequences:

1. Posting is the one job an ordinary app can do legitimately. That is why the API-based servers below are all publishing tools.
2. Company pages need an approved app. A server that makes you register your own developer app will usually only post to your personal profile, because a new app does not have Community Management access.
3. If a server sends DMs, sends connection requests or searches people, it is almost certainly driving a browser. That is not automatically wrong, but it is the category LinkedIn's User Agreement restricts, and it is where the account risk sits.

Pick by job, not by star count

• Publish your own posts from Claude or ChatGPT. Use a hosted server that connects through LinkedIn's API with its own approved app: you sign in once with OAuth and never handle a token. Antwork, Postiv, Kalovio, 2pr.io, Taplio and PostMCP are in this group.
• Post as the last step of an automation (a closed deal, a new blog post). Composio or Zapier, where LinkedIn is one connector among many.
• Research profiles, search people, read your inbox. stickerdaniel/linkedin-mcp-server (free, local) or Linked API (hosted, paid). Both automate a browser. Read their warnings before pointing them at an account you care about.
• Bulk profile data. Apify runs scraper actors and bills per result. It publishes nothing.
• Just schedule LinkedIn posts, with or without an AI app. LinkedIn's own composer can schedule too; how to schedule LinkedIn posts compares that with scheduling from Claude or ChatGPT.

Publishing servers, one by one

Research and outreach servers

stickerdaniel/linkedin-mcp-server is the most popular LinkedIn MCP on GitHub and the most capable reader: profiles, people search, your feed, your inbox, sending messages and connection requests. It works by driving a browser logged in as you, and its README is direct about the risk: "LinkedIn's User Agreement prohibits automated access, and accounts using automated tools can be restricted or banned." It does not publish posts.

Linked API offers similar reach as a hosted service, running "a dedicated cloud browser on an account you own", including Sales Navigator tools. It comments and reacts but has no create-post tool.

Apify is an extraction platform: profile data and email discovery, billed per result, with no LinkedIn cookies required and no publishing.

If your goal is posting, none of these three is the right tool, however many stars they have.

How to connect a LinkedIn MCP server

The steps are the same for any hosted server. Here they are with Antwork's URL; swap in your vendor's.

• Claude (claude.ai and Claude Desktop): Settings → Connectors → Add custom connector, paste https://api.antwork.io/mcp, then sign in with LinkedIn when asked. The full walkthrough, with what Claude shows you before anything posts, is in how to connect Claude to LinkedIn.
• ChatGPT: Antwork is an official app in ChatGPT's directory: open its listing, click Connect, sign in and approve. The walkthrough is in how to connect ChatGPT to LinkedIn. For a server that is not listed, turn on Developer mode in Settings → Security and login, open Plugins in the sidebar, click +, and paste the URL. ChatGPT only accepts remote servers, so local GitHub servers will not work here.
• Claude Code: run claude mcp add antwork --transport http https://api.antwork.io/mcp, then /mcp to sign in.
• Cursor: add the URL as a remote MCP server in Cursor's MCP settings.

Then ask something concrete: "Draft a LinkedIn post about what we shipped this week, in the style of my last posts, and schedule it for Tuesday at 9."

Before you give an AI publish rights

• Prefer OAuth over pasted tokens. An OAuth grant can be revoked from LinkedIn's settings. A token pasted into a config file lives wherever that file goes.
• Keep a review step. An assistant with publish rights and an untrusted document in its context (an email, a web page) can be talked into posting. Choose a server that creates drafts and publishes only on an explicit request.
• Format before you schedule. LinkedIn has no bold or italic button. The LinkedIn text formatter styles a line with Unicode characters, which LinkedIn shows as pasted, and previews where the post folds behind "see more".
• Know the ceiling. Share on LinkedIn allows 150 requests per member per day. No tool gets around that, and none should try.
• Match the tool to the job. Use a browser-automation server only for work that genuinely needs it, and never on an account you cannot afford to lose.