Post to Facebook 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 Facebook, and what Facebook 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 Facebook 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 Facebook tools Perplexity gets

• post_to_meta — publishes to the Page — text, an image, a video, or a multi-photo post — and takes pageId so it never has to guess which Page.
• schedule_post — queues the same post for a time you choose, on one calendar shared with every other channel.
• list_meta_pages — lists the Pages the account has connected, with their ids.
• manage_meta_post — edits the copy of a published post, or deletes it.
• list_meta_comments / reply_to_meta_comment / moderate_meta_comment — reads the comments under a post, replies as the Page, and hides or deletes what should not be there.
• meta_page_insights / meta_post_insights — Page-level and per-post reach, impressions and engagement.
• upload_meta_asset — puts a finished render into the ad account’s asset library.

Facebook is also the one channel with native remote scheduling — post_to_meta takes a scheduleAt between ten minutes and thirty days out and hands the timing to Meta itself. Instagram and Threads have no such thing in Meta’s API, and passing it for them is refused rather than quietly posted immediately.

Facebook limits worth knowing before you automate anything

Try it in Perplexity

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

“Find what our category’s longest-running Facebook ads have in common, make a 4:5 image ad from that angle, and hold it on our Page as an unpublished draft.”

That walks find_competitors → search_meta_ads → plan_ad → render_ad → list_meta_pages → post_to_meta. 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 Facebook: the part that bites

Research is where Perplexity is strongest, and search_meta_ads reads the Meta Ad Library itself, so the answer rests on what competitors are running rather than on articles about them. Ask for a draft on the publishing side. A Facebook draft is a real unpublished Page post you can check in Business Suite, and a published one can still be edited or deleted.

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 Facebook before you post

The Meta Ad Library is the richest public creative archive there is, and search_meta_ads reads it — by keyword or by page — covering both Facebook and Instagram placements. pull_competitor_ads and competitor_teardown build on it, and find_competitors works out who to point them at.

The paid half

Facebook is the deepest paid surface Hermoso has. create_meta_campaign, create_meta_adset and create_meta_ad build the whole tree with real targeting — geography down to a city radius, interests, behaviours, custom audiences and lookalikes, placements, dayparting, bid and cost caps. Everything is created PAUSED with no caller override, and the summary your agent reports is built from a read-back of what Meta actually stored, never from what was requested. Before a budget is committed, preview_meta_ad renders the real ad per placement as a link you can look at and estimate_meta_reach says how many people the targeting actually reaches. One warning that saves money: an ad set created with no locations defaults to the United States only, and the read-back says so loudly.

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

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

Frequently asked questions

Can Perplexity post to Facebook?

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 Facebook — and the ones that research the ads already running in your market and render the creative in the first place.

How do I connect Facebook 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 Facebook inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Perplexity publishes to Facebook as an ordinary tool call.

Can Perplexity post privately or as a draft to Facebook?

Yes. Facebook is the one channel with a genuine draft: an unpublished Page post that exists in Meta Business Suite and that nobody outside can see. Hermoso refuses a visibility Facebook cannot honour at the moment you ask for it, rather than quietly publishing something weaker.

What does it cost to post to Facebook from Perplexity?

Publishing to Facebook costs no credits — Meta charges nothing per API call. Credits are spent on generation: rendering the image or video the post carries. 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.