Last updated: September 2026

Is there an official LinkedIn MCP server?

No. As of September 2026, LinkedIn does not publish an official MCP server. What exists are third-party servers of three kinds: ones that drive a logged-in browser session, ones that wrap the LinkedIn API with a developer app you register, and hosted servers such as OpenTweet's that post through the official LinkedIn API and also cover X and Bluesky.

Which kind a server is decides what it can reach and what it puts at risk, so that comes first. Then the setup for the official-API route.

The three kinds of LinkedIn MCP server

None of them is from LinkedIn. They differ in how they reach LinkedIn.

Kind
How it reaches LinkedIn
What it can reach
What you set up
Account risk
Browser-session servers
Drive a logged-in browser or reuse its session
Whatever the website shows, which is more than the API
A browser kept logged in to LinkedIn
Automated access the User Agreement prohibits. The account can be restricted
Self-hosted API wrappers
Call the LinkedIn API with your own developer app
What your app is granted. For your own profile, posting
A LinkedIn developer app with Share on LinkedIn, and a member token that lasts 60 days with no refresh token
The sanctioned route
OpenTweet hosted MCP
Calls the LinkedIn posting API through the OpenTweet LinkedIn app
Posts and schedules to your personal profile, plus X and Bluesky from the same call
An ot_ key in your MCP config and one LinkedIn sign-in in Settings
The sanctioned route

A server-by-server breakdown is in LinkedIn MCP servers compared.

Why the most popular one is a browser-session server

As of September 2026, the most-starred LinkedIn MCP repository on GitHub, stickerdaniel/linkedin-mcp-server, drives a logged-in browser session, and its own README flags the terms-of-service risk. Working the website is how it reaches profiles and pages the posting API does not expose. It does not publish posts through the LinkedIn API.

The trade-off is written into the LinkedIn User Agreement. Section 8.2, item 13 prohibits using “bots or other unauthorized automated methods to access the Services”, and section 3.4 lets LinkedIn restrict or suspend an account that breaches it. The account on the other end of the session is yours.

The server is not the one that gets restricted

A browser-session server takes on no risk of its own. Whatever LinkedIn decides about the automated access lands on the member account the session belongs to. The longer version is in is scheduling LinkedIn posts safe.

The official-API route, hosted

OpenTweet runs a hosted MCP server at https://mcp.opentweet.io/mcp. On LinkedIn it posts through the official API via the self-serve Share on LinkedIn product, scope w_member_social, to your personal profile. You connect LinkedIn once in Settings > Accounts with one LinkedIn sign-in, and your MCP config holds only an OpenTweet key.

claude code
claude mcp add --transport http opentweet \
  https://mcp.opentweet.io/mcp \
  --header "Authorization: Bearer ot_your_key"

LinkedIn is one value in the platforms field of the posting tools, not a separate server. The same call can target X and Bluesky too.

tool calls
opentweet_create_tweet({
  text: "We moved deploys to Tuesday mornings. Here is what broke first.",
  platforms: ["linkedin"],
  scheduled_date: "2026-09-22T14:00:00Z"
})

// Same draft, all three networks
opentweet_create_tweet({
  text: "Release 2.4 is out. Notes in the changelog.",
  platforms: ["x", "bluesky", "linkedin"],
  publish_now: true
})

// Where would a post with no platforms value land?
opentweet_list_platforms({})

Config for Claude Desktop, Cursor and other clients is on the LinkedIn MCP server page.

What the official-API route does not do

It does less than a logged-in browser, and the limits are worth knowing before you pick it.

  • Personal profile only. No Company Pages.
  • 3,000 characters per post. A thread becomes one post.
  • No video on LinkedIn yet. Hashtags and mentions publish as plain text.
  • Nothing is read back: no feed, no messages, no LinkedIn analytics.
  • No connection requests, DMs, likes or comments, by design.
  • The LinkedIn sign-in lasts 60 days, then a one-click reconnect.

7-day free trial. Cancel anytime.

Frequently asked questions

Is there an official LinkedIn MCP server?

No. As of September 2026, LinkedIn does not publish an official MCP server. Every LinkedIn MCP server available is third-party: some drive a logged-in browser session, some wrap the LinkedIn API with a developer app you register yourself, and hosted ones such as OpenTweet post through the official LinkedIn API on your behalf.

Is a LinkedIn MCP server that uses my browser session safe?

It carries account risk. The LinkedIn User Agreement, section 8.2 item 13, prohibits bots or other unauthorized automated methods to access the Services, and section 3.4 lets LinkedIn restrict or suspend an account that breaches it. The most-starred LinkedIn MCP repository flags this terms-of-service risk in its own README.

Which LinkedIn MCP server posts through the official API?

The OpenTweet hosted MCP server at https://mcp.opentweet.io/mcp posts to your personal LinkedIn profile through the official LinkedIn API, after one LinkedIn sign-in in Settings > Accounts. The same 43 tools also post to X and Bluesky, selected with a platforms field on the tool call.

Can a LinkedIn MCP server post to a Company Page?

Not through OpenTweet. It posts to the connected member personal profile only. Company Page posting through the LinkedIn API needs the Community Management API, which LinkedIn reviews before granting access.

Can an official-API MCP server read my LinkedIn feed or messages?

Not the OpenTweet one. On LinkedIn it publishes and schedules posts, and nothing is read back: no feed, no messages, no comments, no analytics. It also sends no connection requests, DMs, likes or comments, by design.

A LinkedIn MCP server on the official API

Hosted, 43 tools, LinkedIn plus X and Bluesky from one call. From $11.99 a month.

7-day free trial. Cancel anytime.