Hermoso is a marketing MCP server: 301 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 Code reaches all of it through one connection. This page is about one slice of that — what Claude Code can actually do on Threads, and what Threads will not let it do.
Connect Hermoso to Claude Code
- Create an API key. In Hermoso, open Settings → Agents & API keys and press ＋ Create API key. It looks like
hmk_…and carries real spend authority, so treat it like a password. - Add the server.
claude mcp add --transport http hermoso https://app.hermoso.ai/mcp \ --header "Authorization: Bearer <your key>" - Or run it over stdio if you would rather not hold an HTTP config:
claude mcp add hermoso -e HERMOSO_TOKEN=hmk_… -- npx -y hermoso mcp - Ask Claude Code 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.
Both forms reach the same 301 tools. The HTTP form is the hosted server; the stdio form runs the published hermoso npm package locally and talks to the same account.
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 Code gets
post_to_meta— publishes withtarget: "threads"— text, image or video, and 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 is what makes it usable as a listening channel and not just 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 except X. It is enforced when the post is created or queued — refused while you are still there to fix it, rather than 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 Code
Ask for it in ordinary language — these are sentences, not a DSL:
“Generate ten Threads posts under 500 characters from the angles in ./research/angles.md, post the top three, and check mentions every hour for the rest of the day.”
That walks get_brand → generate_text → post_to_meta (target: "threads") → list_threads_replies. Claude Code asks before it runs a tool, and the transcript is right there in the terminal — so a publish step is a line you can read before you press y.
Claude Code on Threads: the part that bites
A terminal session is the right shape for the listening half. list_threads_mentions, list_threads_replies and threads_insights return structured results, so a loop that polls, drafts replies and waits for your approval is a short script rather than a product. Watch the 500-character cap when you generate in bulk — it is enforced at enqueue, so a batch fails fast rather than at fire time.
A 301-tool manifest is not free in context. For long unattended runs the hermoso CLI is the cheaper path: the agent shells out per command instead of carrying the whole manifest.
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 and ChatGPT Ads.
What Claude Code 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 Claude Code, post to: Facebook · Instagram · TikTok · YouTube · X · LinkedIn · Pinterest — or see everything Claude Code can publish to.
Post to Threads from: Claude · ChatGPT · Cursor · Codex · Cline · OpenClaw · Hermes · Claude Code marketing
Frequently asked questions
Can Claude Code post to Threads?
Yes, through Hermoso's MCP server. Create an API key in Hermoso under Settings → Agents & API keys, then add https://app.hermoso.ai/mcp to Claude Code with an Authorization: Bearer header. Claude Code then has 301 tools, including the ones that publish to Threads — and 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 Code?
Two steps, once each. Create an API key in Hermoso under Settings → Agents & API keys, then add https://app.hermoso.ai/mcp to Claude Code with an Authorization: Bearer header. Then connect Threads inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Claude Code publishes to Threads as an ordinary tool call.
What is the Threads caption limit when posting from Claude Code?
A Threads post is capped at 500 characters — the tightest of any channel here except X. Hermoso enforces it when the post is created or queued, so Claude Code is told immediately rather than failing later when nobody is watching.
What does it cost to post to Threads from Claude Code?
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 — 25 credits at signup and 250+ more to earn, and every feature on every plan.
Start free → See pricing