LinkedIn · from any AI chat
LinkedIn MCP: post from your AI chat.
The network with the most room for words, reachable from the chat where you were already writing them.
Most of what turns up under “LinkedIn MCP server” reads LinkedIn rather than writes to it, and a good share of it works by driving a logged-in browser session — which LinkedIn’s terms do not allow, and which breaks whenever the page changes. This one is built for publishing, and it does that through LinkedIn’s own posting API on access you grant in a browser. Nothing logs in as you, and nothing reads your feed or your messages, from ChatGPT, Claude or Codex alike.
LinkedIn gives you 3,000 characters, which is more than almost anything you will write in a chat window, and up to 9 images alongside. That headroom changes what cross-posting means here: a piece written to be a thread elsewhere arrives on LinkedIn whole, as one post, because the network has no reply chains and the ceiling swallows the whole thing comfortably.
Posting goes to a Page you selected when you connected the account, through LinkedIn’s own API, on a token you granted in a browser. Ask your agent to publish and the result comes back per network — LinkedIn is one of the few where we can also confirm the post exists by reading it back from the public page rather than taking the provider’s word for it.
Asking for a LinkedIn post
The ceilings in this exchange are read from the same table the publisher enforces, so what the agent says here is what would really happen to your LinkedIn post.
Set me up — what do you need?
Just the accounts. Connect them in the browser once and I can publish from here after that.
Done, connected
I will tell you before publishing if a network cannot take what you wrote.
Good. Drafting the launch note now
Send it over and I will check it before anything goes out.
Turn the launch thread I wrote for X into a LinkedIn post and put it out now
attached draft · 640 characters · 1 image
LinkedIn takes it as one piece. Here is what that means:
Published. The post reads back from the public page, so that is checked rather than assumed.
What LinkedIn allows
Read from the same table the publisher enforces, so this cannot drift from what actually happens when you press send.
- Caption limit
- 3,000 characters
- Post with no image or video
- Fine
- Reply chains
- No — the parts are joined into one post
- Images or video per post
- 9
- Image formats
- Anything we accept for upload
Works from ChatGPT, Claude, Cursor, Claude Code, OpenClaw and Hermes, and equally from Codex and Gemini — or any other client that can add a remote MCP server. The address and setup snippets are on the MCP page.
What you can do with LinkedIn from a chat
Long pieces arrive whole
With 3,000 characters available, writing that had to be cut down for a tighter network lands here in full rather than in fragments.
Several images per post
Up to 9 attachments alongside the text, sent in the same instruction that carries the words.
Deletion that means it
A removal is confirmed twice over here — the request succeeds and LinkedIn itself stops serving the post. Not every network on this list can say that.
The Page is your choice
Which Page you publish as is a deliberate second step when you connect, not something guessed from whichever account happened to authorise.
How it works
Connect once
~2 minLink the accounts you use in a browser. OAuth, no passwords typed into a chat, no API keys to paste anywhere.
ChatGPT
Claude
Cursor
Ask, in your own words
one sentenceTell your AI chat to publish to LinkedIn, now or on a day you name. No dashboard, no tab switch.
Read the receipt
per networkOne line per network — what landed, what failed and why, and what genuinely could not be determined.
Two steps to connect, and the first one can fail in silence
Connecting LinkedIn happens in two stages, because after you authorise the account you still have to choose which Page to publish as. The first time we ran it the second stage never completed, and nothing anywhere said so — the account appeared neither at our publishing provider nor in our own database, and the connection screen simply looked unfinished. It is now the one connection flow we check the far end of rather than trusting the redirect, because a silently half-connected account is indistinguishable from a working one right up until you publish.
A limitation of our publishing provider, not of LinkedIn — it goes away if we move. Measured on a live account, 2026-07-27.
When this is the wrong tool
There are no reply chains on LinkedIn, so a multi-part post is joined into one — usually the right outcome given the ceiling, but not if you specifically wanted a chain. LinkedIn also rate-limits public reads hard enough that two requests in a row return an empty 429, and we have never once requested LinkedIn analytics, so numbers for it are not something we can show you yet.
Questions people actually ask
Is there an official LinkedIn MCP server?
Not from LinkedIn, as of October 2026. The popular community servers either drive your logged-in session in a headless browser, which LinkedIn’s terms prohibit, or expect you to get an app of your own approved for LinkedIn’s posting API first. Here that access is already arranged, so connecting is a sign-in rather than a developer application.
Does 1Social post to my personal profile or a company Page?
To the Page you pick during connection. The choice is a deliberate second step in the flow rather than something inferred for you.
What happens to a thread I wrote for X when it reaches LinkedIn?
It arrives as one post. LinkedIn has no native reply chain, so the parts are joined — and with 3,000 characters available, almost any thread fits without being trimmed.
Can a LinkedIn post be deleted after publishing?
Yes. Deletion is confirmed twice over here: the provider reports it, and LinkedIn itself stops serving the post. It is one of the networks where a delete request means what it says.
Something else? Ask us — a person answers.
Read next
Start where you already work.
Connect an account and post your first update in about two minutes. Every plan starts with a free trial.
Posts go out through each network’s official API — not scraping.