Post to LinkedIn from Hermes

Hermoso is a marketing MCP server: 922+ 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. Hermes reaches all of it through one connection. This page covers one slice of that: what Hermes can actually do on LinkedIn, and what LinkedIn will not let it do.

Connect Hermoso to Hermes

1. Install and sign in.

   npm install -g hermoso && hermoso auth login

   Your browser opens once. Nothing to create and nothing to paste: the credential is stored owner-only in ~/.hermoso/config.json. On a machine with no browser, hermoso auth login --token hmk_… takes a key from MCP & CLI → Terminal & API keys instead.
2. Add it to ~/.hermes/config.yaml. mcp_servers is a top-level key, not nested under mcp, and no key goes in the file because hermoso mcp reads the sign-in above:

   mcp_servers:
     hermoso:
       command: "npx"
       args: ["-y", "hermoso", "mcp"]

3. Ask Hermes 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.

Hermoso is not affiliated with or endorsed by the makers of Hermes and does not claim to be. The shape above is quoted from the project's own MCP reference in NousResearch/hermes-agent, read on 2026-08-23; it is documented rather than run here, which is why it is the published file shape and not a bespoke install command.

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 Hermes 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, carrying linkedinOrganizationId so 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

Try it in Hermes

Ask for it in ordinary language. These are plain sentences, not a DSL:

“Publish the weekly summary to the company Page with the three best screenshots as a carousel and alt text on each.”

That walks list_linkedin_pages → plan_ad → render_ad → post_to_linkedin_page → linkedin_page_analytics. Approval behaviour is yours to configure. Hermoso’s own guarantees do not depend on it: campaigns are born paused, spend switches are confirm-gated, and no generation call runs without a verified account behind it.

Hermes on LinkedIn: the part that bites

Resolve list_linkedin_pages once and store the id. The identity rules are enforced on the server rather than in a UI, so an automated run genuinely cannot post to a Page you have not shared. Discovering that at run time is avoidable, though, and a carousel needs the Page id anyway because multi-image posts come from company Pages.

For unattended runs the hermoso CLI with --json is easier to assert on than a tool manifest, and much cheaper in context.

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 Hermes 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 Hermes, post to: Facebook · Instagram · Threads · TikTok · YouTube · X · Pinterest · Bluesky · Telegram. Or see everything Hermes can publish to.

Post to LinkedIn from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Grok Bot · Gemini CLI · Perplexity · Le Chat · Claude Cowork · Perplexity Computer · Paperclip

Frequently asked questions

Can Hermes post to LinkedIn?

Yes, through Hermoso's MCP server. Run npm install -g hermoso && hermoso auth login, then add hermoso under the top-level mcp_servers key in ~/.hermes/config.yaml with command "npx" and args ["-y", "hermoso", "mcp"]. The browser sign-in stores the credential, so no key goes in the file. Hermes then has 922+ 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 Hermes?

Two steps, once each. Run npm install -g hermoso && hermoso auth login, then add hermoso under the top-level mcp_servers key in ~/.hermes/config.yaml with command "npx" and args ["-y", "hermoso", "mcp"]. The browser sign-in stores the credential, so no key goes in the file. Then connect LinkedIn inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Hermes publishes to LinkedIn as an ordinary tool call.

Can Hermes 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 Hermes 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 eleven channels that queue.

What is the LinkedIn caption limit when posting from Hermes?

A LinkedIn post is capped at 3,000 characters. Hermoso enforces it when the post is created or queued, so Hermes is told immediately rather than failing later when nobody is watching.

What does it cost to post to LinkedIn from Hermes?

Publishing to LinkedIn costs no credits; LinkedIn charges nothing per API call. Credits are spent on the render. Plans are $29, $69 and $149 a month for 1,200, 3,000 and 7,000 credits, and every feature is on every plan including Free. The only exception is enterprise SSO.