Claude Code turns what you shipped (the README, the commits, the release notes) into a LinkedIn post in the voice of your recent ones, shows it to you in the terminal, and schedules or publishes it once you approve.
Free for 2 social accounts. No card, no API key.
Write a LinkedIn post announcing our autumn menu, 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.
Saved as a draft in Antwork.
Open in AntworkAsk Claude Code things like these. It shows you the post before anything is scheduled or published.
“Post this menu PDF to our company page as a carousel, with a short intro.”

Profile or company page. Attach images, a video or a PDF; a PDF goes out as a swipeable document post.
“Make the first line a stronger hook.”
Claude Code reads your recent posts first: a Company Page's from LinkedIn, a profile's from what you published through Antwork.
“Schedule it for Tuesday at 8am.”
Publish now or give a day and time. It sits in Antwork's calendar, where you can move or cancel it.
“Which of my last ten posts got the most comments?”
Antwork pulls each post's numbers from LinkedIn every few hours.
“My post failed to publish. Find out why and retry it.”
A failed post comes back with the reason. Retrying it is one message.
Yes, through a connector.
Claude Code can post to LinkedIn through Antwork, a hosted Model Context Protocol (MCP) server. Run claude mcp add antwork --transport http https://api.antwork.io/mcp, type /mcp in Claude Code to approve Antwork in the browser, then ask Claude Code to connect LinkedIn and approve it once on LinkedIn's own consent screen. From then on Claude Code drafts, schedules and publishes posts to your personal profile or a Company Page you manage, from the terminal. Antwork calls LinkedIn's official API with the scopes you granted, so there is no API key, no LinkedIn developer app to register and no session cookie to hand over.
LinkedIn MCP servers compared: which post through the official API, and which drive your browserLinkedIn text formatter: bold, italic and lists for the post, before you schedule itA few minutes, in Claude Code on the web or the desktop app. Needs Claude Pro, Max, Team, or an API key.
Claude Code 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 Code 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 Code and see the post, the connector is the shortest path.