Post to LinkedIn from Perplexity

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

Connect Hermoso to Perplexity

1. Copy the connector URL. https://app.hermoso.ai/mcp
2. Perplexity → Account settings → Connectors → + Custom connector → Remote. Name it Hermoso, paste the URL as the MCP Server URL, set Authentication to OAuth and Transport to Streamable HTTP, tick the acknowledgement and press Add.
3. Click the Hermoso card to connect. Sign in with your Hermoso account on the consent page. The Client ID and Client Secret fields stay empty: Perplexity reads Hermoso’s OAuth endpoints from its discovery document and registers itself.
4. Ask Perplexity 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.

Custom connectors are on Perplexity’s paid plans. In an Enterprise organization, members can add their own only if an admin has switched on Allow members to add custom connectors, which is off by default, and an admin can instead add Hermoso once for everyone. The steps and field names are quoted from Perplexity’s help center article on custom remote connectors, read on 2026-09-23. Hermoso is not affiliated with or endorsed by Perplexity.

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 Perplexity gets

• post_to_linkedin_page — publishes to a company Page — text, an image, a video, or a multi-image post — 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 Perplexity

Ask for it in ordinary language — these are sentences, not a DSL:

“Write a LinkedIn post for our company Page on what changed in our market this quarter, with sources, and publish it with a 4-image carousel of the charts.”

That walks list_linkedin_pages → plan_ad → render_ad → post_to_linkedin_page → linkedin_page_analytics. How Perplexity confirms a tool call is Perplexity’s setting, not ours. Hermoso’s own gates hold either way: campaigns are born paused, spend switches and deletes need an explicit confirmation, and every render is priced before it runs.

Perplexity on LinkedIn: the part that bites

In a Perplexity Enterprise organization an admin can add Hermoso once for everyone, and choose between one sign-in for the whole org or a sign-in per member. Pick per member. One shared sign-in would put everyone on one Hermoso account, its credits and its brand, and which LinkedIn Pages a person may post to is decided per person for a reason.

Choose Streamable HTTP, not SSE, when you add the connector. Hermoso has no SSE endpoint, so an SSE connector fails the check Perplexity runs when you save it. In an Enterprise org, a connector an admin adds does not show up for members until it is shared from the Permissions screen.

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

Post to LinkedIn from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Grok Bot · Hermes · Gemini CLI · Le Chat

Frequently asked questions

Can Perplexity post to LinkedIn?

Yes, through Hermoso's MCP server. In Perplexity, add https://app.hermoso.ai/mcp as a custom connector and approve it with your Hermoso account — there is no key to paste. Perplexity then has 850+ tools, including the ones that publish to LinkedIn — and 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 Perplexity?

Two steps, once each. In Perplexity, add https://app.hermoso.ai/mcp as a custom connector and approve it with your Hermoso account — 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 Perplexity publishes to LinkedIn as an ordinary tool call.

What is the LinkedIn caption limit when posting from Perplexity?

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

What does it cost to post to LinkedIn from Perplexity?

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.