Last updated: September 2026
LinkedIn MCP servers compared: official API vs browser session
LinkedIn publishes no official MCP server as of September 2026, so every LinkedIn MCP server is third party, and they reach LinkedIn in one of two ways. Some use the official API with an OAuth sign-in. Others drive your logged-in browser session, which reaches more of the site but is the kind of automated access the LinkedIn User Agreement prohibits.
If you want an agent to publish and schedule posts, the API route is the one built for it. The most-starred browser-session server has no post-publishing tool at all, per its README. This comparison is written by OpenTweet, which is one of the options below. Claims about other projects are limited to what their own documentation says as of September 2026.
LinkedIn MCP servers side by side
Four rows: one named browser-session server, the self-hosted API wrappers as a category, Zapier, and OpenTweet.
| Server | How it authenticates | Can publish posts | Can schedule | Other networks | Hosted or local | Terms-of-service risk |
|---|---|---|---|---|---|---|
| stickerdaniel/linkedin-mcp-serverBrowser session | Your logged-in LinkedIn session, in a browser the server automates | No post-publishing tool in its README tool list | No | None, LinkedIn only | Local, on your machine | Flagged by its own README: automated access may violate LinkedIn terms and can lead to account restrictions |
| API-wrapper servers you run yourselfOfficial API, your own app | Official OAuth, through a LinkedIn developer app you create and tie to a LinkedIn Page | Yes, to your personal profile with w_member_social | Only if the server keeps its own queue and stays running | Depends on the project | Local, you run it | Official API. You hold the token and repeat the sign-in every 60 days |
| Zapier’s LinkedIn actions through its MCPAutomation platform | A LinkedIn connection you authorize in your Zapier account | Check Zapier’s current LinkedIn action list | Check Zapier’s current LinkedIn action list | Other Zapier apps, each connected in Zapier | Hosted by Zapier | Not a browser session you hand over |
| OpenTweetOfficial API, hosted | Official OAuth API. You approve on linkedin.com; your MCP config holds only an OpenTweet key | Yes, to your personal profile. Text and images, no video yet | Yes, scheduled_date on the tool call | X and Bluesky, in the same call | Hosted at mcp.opentweet.io/mcp, or local via npm | Official API on the self-serve Share on LinkedIn product |
The stickerdaniel/linkedin-mcp-server row reflects its README as of September 2026. For Zapier, check its current LinkedIn action list before relying on a specific action. A self-serve LinkedIn app cannot post as a Company Page; that needs the Community Management API and LinkedIn review.
The two ways a server reaches LinkedIn
Official API with OAuth
- You approve an app on linkedin.com; your password never leaves LinkedIn
- Posting to your own profile needs only the self-serve Share on LinkedIn product
- Publishes text and image posts through the LinkedIn Posts API
- Tokens last 60 days with no refresh token, so the sign-in repeats
- Does less than a logged-in browser. On self-serve access, it posts
Your browser session
- The server controls a browser you are logged into, or reuses its session
- Reaches whatever the website shows, which is why some servers take this route
- Runs on your machine, and only while the browser session is alive
- The User Agreement, section 8.2 item 13, prohibits "bots or other unauthorized automated methods to access the Services ... create, comment on, like, share, or re-share posts"
- The account on the other end of the session carries the risk
If a server asked for your LinkedIn session cookie
Sign out of LinkedIn in that browser, which ends that session, and change your password if you pasted the cookie anywhere it could have been copied.Which should you choose?
Five checks before you connect any of them
- How it reaches LinkedIn. If it asks for your session cookie or opens a browser logged in as you, it is automating the website.
- Whether it has a tool that creates a post at all. Several LinkedIn servers are built for reading.
- Whether it schedules, or only posts while the agent is running.
- Where the LinkedIn secret lives: your config file, a local browser profile, or a server-side grant.
- Who handles the 60-day sign-in, and what happens to queued posts when it lapses.
The OpenTweet row, in practice
Connect LinkedIn once in Settings, add the hosted server to Claude Code, and pass platforms on the tools you already use.
claude mcp add --transport http opentweet \
https://mcp.opentweet.io/mcp \
--header "Authorization: Bearer ot_your_key"// Schedule one post to LinkedIn only
opentweet_create_tweet({
text: "We moved deploys to Tuesday mornings. Here is what broke first.",
platforms: ["linkedin"],
scheduled_date: "2026-10-01T09:00:00Z"
})
// One draft, three networks, right now
opentweet_create_tweet({
text: "Release 2.4 is out. Notes in the changelog.",
platforms: ["x", "bluesky", "linkedin"],
publish_now: true
})
// Where would an unpinned post land?
opentweet_list_platforms({})On LinkedIn: personal profile only, 3,000 characters, a thread becomes one post, no video yet, hashtags as plain text, and no LinkedIn analytics, DMs, connections or comments. The sign-in lasts 60 days and then reconnects in one click. Prefer a local process? The same server ships on npm as @opentweet/mcp-server. Full setup on the LinkedIn MCP page.
Frequently asked questions
Is there an official LinkedIn MCP server?
No. As of September 2026 LinkedIn publishes no MCP server of its own. Every LinkedIn MCP server is third party, so the question to ask of each one is how it reaches LinkedIn: through the official API with OAuth, or through your logged-in browser session.
Can stickerdaniel/linkedin-mcp-server publish posts?
Per its README as of September 2026, no. Its tools read profiles, companies, jobs, the feed and the inbox, and send messages and connection requests, but none creates a post. It works by driving a logged-in browser session on your machine, and its README warns that automated access may violate LinkedIn terms and can lead to account restrictions.
Is a browser-session LinkedIn MCP server against LinkedIn terms?
LinkedIn’s User Agreement, section 8.2 item 13, prohibits using "bots or other unauthorized automated methods to access the Services ... create, comment on, like, share, or re-share posts". A server that automates your browser session is automated access to the website, and the account on the other end of that session carries the risk.
Which LinkedIn MCP server works with Claude Code for posting?
Any server that exposes a posting tool over the official LinkedIn API. For OpenTweet it is one command: claude mcp add --transport http opentweet https://mcp.opentweet.io/mcp --header "Authorization: Bearer ot_your_key". The tools opentweet_create_tweet and opentweet_create_thread then take platforms: ["linkedin"].
Can a LinkedIn MCP server schedule posts?
Only if something keeps the post and publishes it later without the agent. The LinkedIn posts call publishes when it is made, so a server you run yourself schedules only if it has its own queue and stays running. OpenTweet stores scheduled_date and publishes at that time from its own queue.
Why do API-based LinkedIn servers need a new sign-in every 60 days?
LinkedIn gives self-serve apps a 60-day access token and no refresh token, so no server on that access can renew it quietly. If you run your own wrapper, you repeat the OAuth flow. On OpenTweet it is a one-click reconnect, scheduled LinkedIn posts are held while the sign-in is expired, and you get an email.
Can any of these post to a LinkedIn Company Page?
Not through a self-serve LinkedIn app. Posting as a Company Page through the LinkedIn API needs the Community Management API, which requires LinkedIn review, so an API wrapper you run on your own app posts to your personal profile only. OpenTweet posts to the personal profile of the member who connected and does not support Company Pages. For Zapier, check its current LinkedIn action list.
Keep exploring
LinkedIn from an agent on the official API, and the questions that come up first.
LinkedIn MCP server
Setup, the config, and what the agent can do on LinkedIn through OpenTweet.
Is there an official LinkedIn MCP server?
The short answer, and what the third-party servers do instead.
Is scheduling LinkedIn posts safe?
Where the official API ends and account risk begins.
Post to LinkedIn with the API in Python
What an API-wrapper server does under the hood, with working Python and Node code.
Why the LinkedIn token expires in 60 days
No refresh token on self-serve apps, and what that means for scheduled posts.
Can I post to LinkedIn without partner approval?
What the self-serve products cover, and what still needs LinkedIn review.
LinkedIn scheduler
The same LinkedIn publishing from the app, in one queue with X and Bluesky.
Cross-posting docs
The platforms parameter, the results array, and per-network limits.
Let your agent post to LinkedIn on the official API
Publish and schedule to LinkedIn, X and Bluesky from one tool call. From $11.99/mo, LinkedIn on every plan.
7-day free trial. Cancel anytime.