Post to Threads from Perplexity

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. Perplexity reaches all of it through one connection. This page covers one slice of that: what Perplexity can actually do on Threads, and what Threads will not let it do.

Connect Hermoso to Perplexity

1. Copy the connector URL. https://app.hermoso.ai/mcp
2. Perplexity → Customize → Connectors. In the left sidebar open Customize, then the Connectors tab → Custom connector (top right) → Add MCP connector.
3. Fill in the connector. Name it Hermoso and paste the URL as the MCP server URL. Expand Advanced: Authentication OAuth, leaving Client ID and Client Secret empty (Perplexity reads Hermoso’s OAuth endpoints from its discovery document and identifies itself with its own client metadata, so there is nothing to create or paste), Transport Streamable HTTP, Network access Public. Tick I understand custom connectors can introduce risks and press Add.
4. Sign in. On the Hermoso card click + (Add connector) and approve on the Hermoso consent page with your Hermoso account.
5. Switch it on in a chat. A custom connector is off until you pick it: + (Add files or tools) → Connectors → tick Hermoso.
6. 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. We ran these steps end to end on 2026-09-28 from a Perplexity Pro account: the connector signed in and answered with the account’s credit balance and brand list. Hermoso is not affiliated with or endorsed by Perplexity.

Then connect Threads 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 Threads tools Perplexity gets

• post_to_meta: publishes text, an image or a video with target: "threads", optionally geotagged.
• schedule_post: queues it alongside every other channel.
• list_threads_posts / threads_insights: what you have posted, and how each one did.
• list_threads_replies / reply_to_thread / hide_thread_reply: read the replies, answer as the brand, hide what does not belong.
• list_threads_mentions: who is talking about you.
• search_threads_keyword / search_threads_locations: keyword search and the location ids a geotag needs.
• delete_thread: removes a post.

Threads is the channel where Hermoso goes furthest past publishing. Beyond posting there is a full read-and-respond surface (replies, mentions, keyword search and per-post insights), which makes it usable as a listening channel as well as an outlet. Note that Threads is a separate OAuth grant from Facebook even though it shares the Page.

Threads limits worth knowing before you automate anything

Try it in Perplexity

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

“Draft three Threads posts under 500 characters from this week’s industry news, post the strongest, and show me today’s mentions.”

That walks get_brand → generate_text → post_to_meta (target: "threads") → list_threads_replies. 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 Threads: the part that bites

Perplexity’s habit of citing sources is worth steering here: a Threads post built on a news item reads better when its claim is one you could link. The 500-character cap is enforced when the post is queued, so a draft that runs long comes back with the overage counted instead of being cut.

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

search_threads searches public Threads by keyword through the research surface, and search_threads_keyword does the same through your connected Threads account. There is no Threads ad library, because there are no Threads ads to archive.

The paid half

There is no Threads ads product in Hermoso, and it would be wrong to imply one. Threads here is an organic channel: publish, read, reply, measure. The paid tools cover Meta (Facebook and Instagram), Google Ads, Microsoft Advertising, Reddit Ads, LinkedIn, Pinterest, X Ads, TikTok Ads, Snapchat Ads, ChatGPT Ads, Apple Search Ads and AppLovin Ads.

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). 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 · TikTok · YouTube · X · LinkedIn · Pinterest · Bluesky · Telegram. Or see everything Perplexity can publish to.

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

Frequently asked questions

Can Perplexity post to Threads?

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 922+ tools, including the ones that publish to Threads, plus the ones that research the ads already running in your market and render the creative in the first place.

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

What is the Threads caption limit when posting from Perplexity?

A Threads post is capped at 500 characters, the tightest of any channel here apart from X. 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 Threads from Perplexity?

Publishing to Threads costs no credits; Meta charges nothing per API call. Credits are spent on generating the creative. 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.

Can Perplexity post privately or as a draft to Threads?

No. Threads has no unlisted, private or draft post; a Threads post is public or it does not exist. Hermoso refuses a visibility Threads cannot honour at the moment you ask for it, rather than quietly publishing something weaker.

Can Perplexity schedule a Threads 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. Threads is one of the eleven channels that queue.