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. Paperclip reaches all of it through one connection. This page covers one slice of that: what Paperclip can actually do on Threads, and what Threads will not let it do.
Connect Hermoso to Paperclip
- Copy the connector URL.
https://app.hermoso.ai/mcp - Paperclip → Connectors → Connect your own MCP server. Paste the URL. Paperclip asks the server what it needs; Hermoso advertises OAuth, so Paperclip registers a client by itself and opens a browser sign-in.
- Approve on the Hermoso page. Sign in with your Hermoso account and allow access. No key is pasted.
- Set the action permissions. Paperclip lists Hermoso’s tools as read, write or destructive, and each can be Allowed, Ask first or Off. Allow the reads, and keep anything that publishes, schedules or spends on Ask first.
- Ask an agent in Paperclip 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.
Paperclip labels any server outside its reviewed catalog an Unverified server, which in Paperclip’s words is a statement about review, not about whether the connection works. Every Hermoso tool publishes read-only and destructive annotations, so the read, write and destructive split comes from the server rather than from Paperclip guessing at tool names. The steps are quoted from Paperclip’s custom MCP server guide, read on 2026-10-03, and documented rather than run here. Hermoso is not affiliated with or endorsed by Paperclip.
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 Paperclip gets
post_to_meta: publishes text, an image or a video withtarget: "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
| Text | A Threads post is capped at 500 characters, the tightest here apart from X. 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. “Threads has no unlisted, private or draft post.” A Threads post exists publicly or not at all. |
| Carousel | 2 to 20 slides, images and video mixed. Both bounds are Meta’s own words, quoted in the table that enforces them: “Carousels must have at least 2” items, and “no more than 20 total images, videos, or a mix of the two.” That makes Threads the most generous mixed-media carousel of any channel here. |
| Which account | pageId. The same connected Page identity carries Facebook, Instagram and Threads. |
Try it in Paperclip
Ask for it in ordinary language. These are plain sentences, not a DSL:
“Community agent: list today’s Threads replies and mentions, draft answers to the questions, and submit each reply for approval.”
That walks get_brand → generate_text → post_to_meta (target: "threads") → list_threads_replies. Paperclip puts its own gate in front of every Hermoso call: each action is Allowed, Ask first or Off. Hermoso’s gates sit underneath: campaigns are born paused, and spend switches and deletes need an explicit confirmation.
Paperclip on Threads: the part that bites
The Threads tools split cleanly for Paperclip’s permissions. list_threads_replies, list_threads_mentions and threads_insights only read and can be Allowed; reply_to_thread and posting speak as the brand and belong on Ask first. Posts are capped at 500 characters, checked when they are queued.
There is a second way to give a Paperclip agent Hermoso, and Paperclip warns that it is different: attaching a server to the agent’s runtime, such as installing Hermoso’s plugin into the Claude Code an agent runs on. That works, but Paperclip’s action permissions and review queue do not sit in front of it. Use the connector when you want Paperclip deciding what an agent may publish.
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 and Apple Search Ads.
What Paperclip 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 Paperclip, post to: Facebook · Instagram · TikTok · YouTube · X · LinkedIn · Pinterest · Bluesky · Telegram. Or see everything Paperclip can publish to.
Post to Threads from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Grok Bot · Hermes · Gemini CLI · Perplexity · Le Chat · Claude Cowork · Perplexity Computer
Frequently asked questions
Can Paperclip post to Threads?
Yes, through Hermoso's MCP server. In Paperclip, open Connectors, choose Connect your own MCP server, paste https://app.hermoso.ai/mcp and approve the sign-in with your Hermoso account. There is no key to paste. Paperclip then has 876+ 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 Paperclip?
Two steps, once each. In Paperclip, open Connectors, choose Connect your own MCP server, paste https://app.hermoso.ai/mcp and approve the sign-in 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 Paperclip publishes to Threads as an ordinary tool call.
What is the Threads caption limit when posting from Paperclip?
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 Paperclip is told immediately rather than failing later when nobody is watching.
What does it cost to post to Threads from Paperclip?
Publishing to Threads costs no credits; Meta charges nothing per API call. Credits are spent on generating the creative. 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.
Can Paperclip 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 Paperclip 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 ten channels that queue.
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