Hermoso is a marketing MCP server: 876+ tools over one OAuth’d endpoint that let an agent research the ads already running in a market, generate finished image and video ads, publish them, and build the paid campaigns behind them. Claude Cowork reaches all of it through one connection. This page covers one slice of that: what Claude Cowork can actually do on LinkedIn, and what LinkedIn will not let it do.
Connect Hermoso to Claude Cowork
- Copy the connector URL.
https://app.hermoso.ai/mcp - Claude → Customize → Connectors → ＋ Add → Add custom connector. Name it Hermoso and paste the URL. Leave the sign-in option on Claude’s default: Hermoso accepts Claude’s published client identity and also registers clients automatically, so there is no client ID to create.
- Connect and approve. Sign in with your Hermoso account on the consent page. No key is pasted.
- Open Cowork and hand it the job. Cowork sees the same connector. Ask it to list your connected channels first, so you know which accounts it can reach.
- Ask Cowork for something. “Pull my three closest competitors’ longest-running ads and remix the best hook into a 9:16 video,” or “post this render to the channel.” The agent picks the tools; you approve the spend.
Anthropic’s help center lists custom connectors on Claude, Cowork and Claude Desktop, and Cowork itself on the paid plans: Pro, Max, Team and Enterprise. On Team and Enterprise an Owner adds Hermoso once under Organization settings, Connectors, and members press Connect. One detail decides the route: a local server in claude_desktop_config.json is not available in Cowork, so the hosted connector is the way in, not npx hermoso mcp. Read from Anthropic’s help center on 2026-10-03. Hermoso is not affiliated with or endorsed by Anthropic.
Then connect LinkedIn itself, once, under Settings → Connectors in Hermoso. That is an OAuth consent screen, so it is the one step that needs a browser. Everything after it is a tool call.
The LinkedIn tools Claude Cowork gets
post_to_linkedin_page: publishes text, an image, a video or a multi-image post to a company Page, with alt text.post_to_linkedin: publishes to a personal profile, which stays switched off until you explicitly share that identity.list_linkedin_pages: the Pages you have shared with this brand, with their organization ids.schedule_post: queues it, carryinglinkedinOrganizationIdso the right identity posts.manage_linkedin_post: edit the copy of a post, or delete it.linkedin_page_analytics: organic Page performance: follower gains, Page views, and post impressions, clicks and engagement, per Page or per post.search_linkedin_ads: the LinkedIn Ad Library, the one public ad library that exposes real impression counts.
LinkedIn is the channel where identity is a permission rather than a preference. One person usually administers several companies’ Pages, so Hermoso makes the postable identities an explicit choice: only the Pages you have ticked under Manage accounts can be posted to, an unticked Page is refused server-side rather than in the UI alone, and the personal profile is off unless you turn it on. An agent that asks which Page rather than assuming is doing the right thing.
LinkedIn limits worth knowing before you automate anything
| Text | A LinkedIn post is capped at 3,000 characters. It is enforced when the post is created or queued, so an overlong post is refused while you are still there to fix it instead of being silently cut on the way out. |
|---|---|
| Visibility | Public only. A LinkedIn post publishes to the profile or the company Page, and “LinkedIn has no unlisted, private or draft post.” |
| Carousel | 2 to 20 images, from a company Page. Both bounds are LinkedIn’s own: “A MultiImage post is a post containing multiple images (minimum of 2 images and maximum of 20 images)”, and the schema adds “Only supports images”. Two refusals follow from that and both are by name rather than by silent downgrade: a video slide is refused because LinkedIn’s multi-image post cannot carry one, and a personal-profile carousel is refused with the way forward: pass linkedinOrganizationId (from list_linkedin_pages), because “a personal-profile carousel is not something Hermoso can publish.” |
| Which account | linkedinOrganizationId. Unset means the member’s own profile, never “probably the company”. The field is how you say which Page, and leaving it out is a decision rather than an accident. |
Try it in Claude Cowork
Ask for it in ordinary language. These are plain sentences, not a DSL:
“Write a LinkedIn post for our company Page about this quarter’s numbers, build a 5-image carousel of the charts, and publish it.”
That walks list_linkedin_pages → plan_ad → render_ad → post_to_linkedin_page → linkedin_page_analytics. How often Cowork stops to check with you is Cowork’s behaviour, not ours. Hermoso’s gates hold either way: campaigns are born paused, and spend switches and deletes need an explicit confirmation.
Claude Cowork on LinkedIn: the part that bites
Which identity posts is decided on Hermoso’s server, not in the task: only Pages you ticked in Hermoso can be posted to, and the personal profile stays off until you share it. Carousels come from company Pages only, two to twenty images, which are LinkedIn’s own bounds.
Cowork can run shell commands, but Anthropic’s default network setting for that sandbox allows package registries rather than every domain, so the hermoso command line is not something to rely on there. The connector is unaffected: Anthropic says connector traffic keeps working whatever the sandbox’s network setting is.
Research LinkedIn before you post
search_linkedin_ads reads the LinkedIn Ad Library, which is unusual among public ad libraries in exposing real impression counts, so B2B competitor research on LinkedIn can be ranked by actual delivery rather than by guesswork about what is running.
The paid half
create_linkedin_ads_campaign_group → create_linkedin_ads_campaign → create_linkedin_ads_creative builds the tree, and everything is born as a draft. set_linkedin_ads_status is the only switch that arms real money and it refuses without an explicit confirmation. One access note that is better said than discovered: LinkedIn meters ad writes by the API tier your own ad account holds. Reporting and reads are unrestricted, and on the development tier an app may edit a small number of ad accounts, each registered by hand.
What Claude Cowork cannot do on its own
An agent with a budget is only useful if the blast radius is bounded, so the fence is in the server rather than in a prompt. Every ad campaign, ad set, ad group and ad is created paused, and the status switches that arm real money refuse to run without an explicit confirmation flag. Every render is quoted first (hermoso_capabilities publishes each model’s exact credit cost before anything spends). Credits are reserved before the first provider call and settled at the exact cost afterwards, so a failed dispatch refunds rather than leaving you billed for nothing. Deletes are confirm-gated too, and every campaign tree is read back from the ad platform before your agent tells you what it built.
One step is deliberately not headless: linking an account is an OAuth consent screen, so you connect the channel once in a browser. Everything after that is a tool call.
The rest of the matrix
From Claude Cowork, post to: Facebook · Instagram · Threads · TikTok · YouTube · X · Pinterest · Bluesky · Telegram. Or see everything Claude Cowork can publish to.
Post to LinkedIn from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Grok Bot · Hermes · Gemini CLI · Perplexity · Le Chat · Perplexity Computer · Paperclip · AI marketing in Claude
Frequently asked questions
Can Claude Cowork post to LinkedIn?
Yes, through the Hermoso connector you add in Claude. In Claude, open Customize, Connectors, add a custom connector with https://app.hermoso.ai/mcp and approve it with your Hermoso account. Cowork uses the same connector, and there is no key to paste. Claude Cowork then has 876+ tools, including the ones that publish to LinkedIn, plus the ones that research the ads already running in your market and render the creative in the first place.
How do I connect LinkedIn to Claude Cowork?
Two steps, once each. In Claude, open Customize, Connectors, add a custom connector with https://app.hermoso.ai/mcp and approve it with your Hermoso account. Cowork uses the same connector, and there is no key to paste. Then connect LinkedIn inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Claude Cowork publishes to LinkedIn as an ordinary tool call.
Can Claude Cowork post privately or as a draft to LinkedIn?
No. LinkedIn has no unlisted, private or draft post. A post publishes to the profile or the company Page. Hermoso refuses a visibility LinkedIn cannot honour at the moment you ask for it, rather than quietly publishing something weaker.
Can Claude Cowork schedule a LinkedIn post for later?
Yes. schedule_post queues it on one calendar shared with every other channel, with a per-channel caption if the copy should differ, and list_scheduled and cancel_scheduled read and pull it back. LinkedIn is one of the ten channels that queue.
What is the LinkedIn caption limit when posting from Claude Cowork?
A LinkedIn post is capped at 3,000 characters. Hermoso enforces it when the post is created or queued, so Claude Cowork is told immediately rather than failing later when nobody is watching.
What does it cost to post to LinkedIn from Claude Cowork?
Publishing to LinkedIn costs no credits; LinkedIn charges nothing per API call. Credits are spent on the render. Plans are $19, $49 and $149 a month for 1,000, 3,000 and 10,000 credits, and every feature is on every plan including Free. The only exception is enterprise SSO.
Start free with 30 credits at signup and 250+ more to earn. Every feature is on every plan. Credits are spent only on AI models and Ad Spy research; posting, scheduling, ads management and analytics are free.
Start free → See pricing