Photo by EVG Kowalievska from Pexels: https://www.pexels.com/photo/1128207/
On October 9, 2026, the documentation of seven social media companies listed below, plus SocialPost, described a live MCP server that can schedule or publish a LinkedIn post from an AI assistant such as Claude or ChatGPT. LinkedIn itself does not publish one: a search of LinkedIn and Microsoft developer pages on that date found no official LinkedIn MCP server. Every LinkedIn MCP server today comes from a third party, so the real choice for a team is which third party, and what that server does before a post goes live.
This page lists each server we found, what its own documentation says it can post, and which ones are still a beta or an announcement. Everything below was checked from public docs and repos on October 9, 2026. We did not install or run any of these servers, so the list records what each vendor says, read on that date.
What an MCP server does for a LinkedIn team
MCP stands for Model Context Protocol. An MCP server is a small connector that lets an AI assistant use another product's features from inside the chat. For social media, the connector usually lets the assistant create a post, put the post in a queue or a schedule, and sometimes publish the post straight away.
For a team, the useful question is narrower than "does a LinkedIn MCP server exist?" The useful question is what happens between the assistant writing the caption and LinkedIn showing the post. A server that publishes the moment the assistant asks is fast. A server that holds the post for a person to approve is safer for a firm whose name is on the post.
Vendor MCP servers that list LinkedIn posting
These servers each had a live connection address and setup instructions on the vendor's own site on October 9, 2026. "Personal or company page" is filled in only where the vendor's page says so.
- Buffer. Status on the vendor's page: Live, connects with an API key. LinkedIn: Listed as a channel. What the docs say it does with a post: Queue, custom time or share now; drafts.
- Hootsuite. Status on the vendor's page: Setup steps published, no beta label. LinkedIn: Listed. What the docs say it does with a post: Schedules posts and saves drafts.
- Typefully. Status on the vendor's page: Live. LinkedIn: Listed. What the docs say it does with a post: Schedules posts; creates and edits drafts.
- Zernio. Status on the vendor's page: Live. LinkedIn: Personal profile and company page. What the docs say it does with a post: Publishes now, schedules or saves a draft.
- Postiz. Status on the vendor's page: Live, open source. LinkedIn: Named in examples. What the docs say it does with a post: Schedules, drafts or publishes now.
- Vista Social. Status on the vendor's page: The address is copied from inside the account. LinkedIn: Shown in examples. What the docs say it does with a post: Schedules posts; examples show approval prompts.
- Publer. Status on the vendor's page: The help article gives two different answers on which accounts get access. LinkedIn: Shown for a LinkedIn Page only. What the docs say it does with a post: Creates drafts and schedules.
Two more vendor servers were live on October 9, 2026, but their pages did not name LinkedIn. Metricool says its server works with any connected network. Ayrshare documents a server that publishes posts, and the pages we read did not list the networks.
Servers that are a beta, a partial tool or an announcement
A few names come up in searches for a LinkedIn MCP server but do something narrower than posting.
- Agorapulse calls its connector a beta. The help article describes draft posts, inbox and analytics.
- Meta publishes official MCP servers, and the Meta developer page we read on October 9, 2026 did not list Facebook or Instagram post publishing among their tools.
- X has an open source MCP server in the xdevplatform/xmcp repository. The repository page describes X only and does not mention LinkedIn.
A warning about open source LinkedIn servers
The most-starred LinkedIn MCP repository on GitHub on October 9, 2026, stickerdaniel/linkedin-mcp-server, works by driving a logged-in web browser. Its own README warns that LinkedIn prohibits automated access and that accounts can be banned. The tool list in the README, read on October 9, 2026, does not include a tool for creating a post. Several smaller repositories use the same browser method. A firm should not connect its own LinkedIn login to a server built this way. Look for a server that uses LinkedIn's official posting API through a vendor account instead.
How the SocialPost MCP server works
SocialPost publishes its own MCP server, documented on the SocialPost MCP page. The split of work is simple. Keep your AI: ChatGPT, Claude or Grok writes the caption. SocialPost renders a brand-correct image with your logo and colors, formats the post for each platform, shows a preview, holds the post for your approval, and schedules the post. You approve every post. Nothing publishes without your sign-off.
The MCP page lists LinkedIn, X, Facebook, Instagram, YouTube and Threads as networks the server can schedule to.
Setup steps
- Create a SocialPost account and connect your LinkedIn account in the SocialPost web app.
- Set up your Brand Kit in the web app, so the server can render images with your logo and colors.
- Copy the connector address, https://api.socialpostai.com/api/mcp/, into your AI app. In Claude, the place to paste the address is Customize, then Connectors. Some AI apps allow custom connectors only on a paid plan of that app, so check your AI app's settings first.
- Sign in to SocialPost when the AI app asks, which links the connector to your account.
- Ask your assistant for a LinkedIn post. Your assistant writes the caption, SocialPost shows the preview for each network, and you approve the post in the chat. A scheduled post has to be at least 10 minutes in the future.
Some work stays in the SocialPost web app: connecting or removing accounts, uploading photos from your device, recurring schedules, analytics, carousels and video posts.
How to choose a LinkedIn MCP server for a team
- Check where the post waits. Read whether the server publishes immediately, saves a draft, or holds the post for a named person to approve.
- Check the login method. Prefer a server that posts through a vendor account using LinkedIn's official API. Avoid any server that asks for your LinkedIn password or browser cookies.
- Check personal profile or company page. Most vendor pages do not say. If your firm posts from a company page, confirm the server supports company pages before you connect it.
- Check the status label. A beta or a "rough edges" note means the tool list can change.
If your team already writes LinkedIn posts with ChatGPT, Claude or Grok, keep that habit. Start free on the Free plan, connect LinkedIn, and approve your first post from inside the chat.
Frequently asked questions
Does LinkedIn have an official MCP server?
A search of LinkedIn and Microsoft developer pages on October 9, 2026 found no official LinkedIn MCP server. Every LinkedIn MCP server found on that date came from a third party.
Can an MCP server post to a LinkedIn company page?
Some can. Zernio's page says its server posts to personal profiles and company pages. Most other vendor pages checked on October 9, 2026 did not say which, so confirm with the vendor before you connect a company page.
Is it safe to connect a LinkedIn MCP server from GitHub?
Check how the server logs in. A server that drives a browser with your LinkedIn login breaks LinkedIn's rules on automated access, and the most-starred repository says so in its own README. A server that posts through LinkedIn's official API through a vendor account does not carry that risk.
Does the SocialPost MCP server publish without approval?
No. Your assistant writes the caption and SocialPost holds the post until you approve the post in the chat. Nothing publishes without your sign-off.
