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. Claude Cowork reaches all of it through one connection. This page covers one slice of that: what Claude Cowork can actually do on Threads, and what Threads will not let it do.
Connect Hermoso to Claude Cowork
- Copy the connector URL.
https://app.hermoso.ai/mcp - Claude → Customize → Connectors → ＋ Add → Add custom connector. Name it Hermoso and paste the URL. Leave the sign-in option on Claude’s default: Hermoso accepts Claude’s published client identity and also registers clients automatically, so there is no client ID to create.
- Connect and approve. Sign in with your Hermoso account on the consent page. No key is pasted.
- Open Cowork and hand it the job. Cowork sees the same connector. Ask it to list your connected channels first, so you know which accounts it can reach.
- Ask Cowork 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.
Anthropic’s help center lists custom connectors on Claude, Cowork and Claude Desktop, and Cowork itself on the paid plans: Pro, Max, Team and Enterprise. On Team and Enterprise an Owner adds Hermoso once under Organization settings, Connectors, and members press Connect. One detail decides the route: a local server in claude_desktop_config.json is not available in Cowork, so the hosted connector is the way in, not npx hermoso mcp. Read from Anthropic’s help center on 2026-10-03. Hermoso is not affiliated with or endorsed by Anthropic.
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 Claude Cowork 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 Claude Cowork
Ask for it in ordinary language. These are plain sentences, not a DSL:
“Post our launch update to Threads under 500 characters, then list today’s replies and mentions and draft an answer to each question.”
That walks get_brand → generate_text → post_to_meta (target: "threads") → list_threads_replies. How often Cowork stops to check with you is Cowork’s behaviour, not ours. Hermoso’s gates hold either way: campaigns are born paused, and spend switches and deletes need an explicit confirmation.
Claude Cowork on Threads: the part that bites
list_threads_replies, list_threads_mentions and threads_insights only read, so a Cowork task can run them freely; reply_to_thread speaks as the brand, so have the task show you its drafts before it replies. The 500-character cap is checked when a post is queued, and an overlong draft comes back with the overage counted.
Cowork can run shell commands, but Anthropic’s default network setting for that sandbox allows package registries rather than every domain, so the hermoso command line is not something to rely on there. The connector is unaffected: Anthropic says connector traffic keeps working whatever the sandbox’s network setting is.
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 Claude Cowork 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 Claude Cowork, post to: Facebook · Instagram · TikTok · YouTube · X · LinkedIn · Pinterest · Bluesky · Telegram. Or see everything Claude Cowork can publish to.
Post to Threads from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Grok Bot · Hermes · Gemini CLI · Perplexity · Le Chat · Perplexity Computer · Paperclip · AI marketing in Claude
Frequently asked questions
Can Claude Cowork post to Threads?
Yes, through the Hermoso connector you add in Claude. In Claude, open Customize, Connectors, add a custom connector with https://app.hermoso.ai/mcp and approve it with your Hermoso account. Cowork uses the same connector, and there is no key to paste. Claude Cowork 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 Claude Cowork?
Two steps, once each. In Claude, open Customize, Connectors, add a custom connector with https://app.hermoso.ai/mcp and approve it with your Hermoso account. Cowork uses the same connector, and 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 Claude Cowork publishes to Threads as an ordinary tool call.
Can Claude Cowork 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 Claude Cowork 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.
What is the Threads caption limit when posting from Claude Cowork?
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 Claude Cowork is told immediately rather than failing later when nobody is watching.
What does it cost to post to Threads from Claude Cowork?
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.
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