Claude drafts your next LinkedIn post in the chat, shows it to you, and schedules or publishes it to your profile or Company Page once you approve. No copying drafts between tabs.
Free for 2 social accounts. No card, no API key.
Write a LinkedIn post announcing our autumn menu, with this photo, in our usual voice.
Checked your connected LinkedIn accountHere's a draft. Nothing goes out until you confirm.

Our autumn menu is in. Three new dishes, one returning favourite, and the pumpkin soup we have been testing since August. Tables for Friday are open now.
Yes, through a connector.
Claude can post to LinkedIn through Antwork, a Model Context Protocol (MCP) connector. You paste one URL into Claude's Add custom connector dialog, approve LinkedIn once on LinkedIn's own OAuth screen, and from then on Claude drafts, schedules and publishes posts to your personal LinkedIn profile or to a Company Page you manage, from inside the conversation. Antwork calls LinkedIn's official API with the scopes you granted (w_member_social for your profile, w_organization_social for Company Pages), so there is no API key to generate, no browser extension to install, and no logged-in browser session being driven on your behalf.
LinkedIn MCP servers compared: which post through the official API, and which drive your browserAbout two minutes, on a computer or in claude.ai in your phone browser. Works on every Claude plan, Free included. The Free plan allows one custom connector. If another one already uses it, remove that one first.
On your phone? Add the connector once in claude.ai in your browser, not in the Claude app. After that it is there in the Claude app too.
Copy one into Claude to try it. Claude always shows you the post before anything is scheduled or published.
Claude checks these before it drafts, so a post does not fail at publish time. They come from the same rules Antwork's publisher enforces.
Each works. They differ in where the work happens and how much you set up.
| Antwork connector | An automation tool | Build your own | |
|---|---|---|---|
| Where you ask | In the Claude chat | In a workflow you build | In your own code |
| Setup | Paste one URL, sign in | Design a scenario per task | Developer app, API access, hosting |
| Writes in your voice | From the posts you made through it | Only what you wire in | Only what you build |
| Schedules and publishes | Yes, from the chat | On the workflow's trigger | If you build it |
| Shows the post first | Every time | Depends on the workflow | Depends on your build |
| Code needed | None | None | Yes |
An automation tool is the better fit when a post should be triggered by something outside the chat, like a new row in a spreadsheet. If you want to ask Claude and see the post, the connector is the shortest path.
Yes. Antwork is the connector: you add one URL to Claude, approve LinkedIn once over OAuth, and from then on Claude drafts, schedules and publishes to your account from the chat itself. No API key, no browser extension, no copying between tabs.
Anthropic does not publish a first-party LinkedIn connector, but Claude supports custom connectors over MCP and Antwork is one. You add it from Claude's own connector settings and its tools become available like any other: no browser extension, no API key, and no intermediate workflow to maintain.
Not an official one. Neither Anthropic nor LinkedIn ships a LinkedIn connector for Claude. Claude supports custom connectors over the Model Context Protocol (MCP), and Antwork is a third-party LinkedIn connector built on it: you add Antwork's server URL in Claude's connector settings, approve LinkedIn once on LinkedIn's own consent screen, and Claude can then draft, schedule and publish posts to your profile or Company Page through LinkedIn's official API.
Through a connector, never a password. Add Antwork as a custom connector in Claude (Customize, then Connectors, then Add custom connector, and paste the server URL), then ask Claude to connect LinkedIn. LinkedIn's own consent screen opens; once you approve it, Claude can publish to your profile or to a Page you manage. What it gets is permission to post and to read the engagement on your own posts, not your inbox or anyone else's profile.
Antwork is not the kind of access LinkedIn restricts, and LinkedIn does not block Claude specifically. What it restricts is automated access to the site itself: the LinkedIn User Agreement prohibits scraping and driving linkedin.com with bots, extensions or browser automation, and that is what most Claude-to-LinkedIn setups are built on. Antwork never touches the website. It calls LinkedIn's official API with a token you granted on LinkedIn's own consent screen, so what LinkedIn sees is an authorized application using the scopes you approved: w_member_social to post as you, w_organization_social to post as a Page you manage.
On the free Claude plan you can add one custom connector, so if another one already uses that slot, the new one cannot be added until you remove it. Pro, Max, Team and Enterprise have no such limit. The option sits under Customize, then Connectors, then Add custom connector. If the dialog is there but Antwork's tools never appear after you add it, the OAuth approval did not finish: open the connector again and complete the browser consent screen.
No. Antwork requests only the scopes it needs to publish on your behalf and to read engagement on your own posts. It never receives your LinkedIn password, it has no messaging scope so it cannot open your inbox or your direct messages, and it cannot look up anyone else's profile. You can revoke the connection from LinkedIn at any time and the token stops working immediately.
What drives the action. In a workflow builder, Claude is a node inside an automation you maintain. With Antwork, drafting, scheduling and publishing to LinkedIn are tools Claude operates directly in the conversation, and the platform's limits are enforced server-side rather than being whatever the flow happens to carry.
No. Antwork connects over OAuth — you approve a consent screen in the browser and you are done. There is no key to generate or paste into a URL, which is how most social MCP servers handle it.
No. Your first two connected accounts are free forever, with unlimited posts and workspaces, and there is no plan gate on MCP access.
Not unless you ask it to. Drafting and publishing are two separate steps: the agent writes, renders the post card, and only publishes when you confirm.
Antwork hands the agent that account's recent posts, along with how each performed, and the agent writes to match them. On LinkedIn that includes writing to the length the format rewards, up to 3,000 characters.
Free for 2 social accounts. Set up in about two minutes.
Connect Claude to LinkedIn