Hermoso is a marketing MCP server: 681+ 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. Cursor reaches all of it through one connection. This page is about one slice of that — what Cursor can actually do on Threads, and what Threads will not let it do.
Connect Hermoso to Cursor
- Install and sign in.
Your browser opens once. Nothing to create and nothing to paste: the credential is stored owner-only innpm install -g hermoso && hermoso auth login~/.hermoso/config.json. On a machine with no browser,hermoso auth login --token hmk_…takes a key from Settings → Agents & API keys instead. - Add it to
~/.cursor/mcp.json(or the project’s.cursor/mcp.json). No key goes in the file, becausehermoso mcpreads the sign-in above:{ "mcpServers": { "hermoso": { "command": "npx", "args": ["-y", "hermoso", "mcp"] } } } - Or use the one-click install from the MCP page. That deeplink installs the hosted URL and leaves authentication to Cursor’s own OAuth flow. Both work, they are just different prerequisites.
- Ask Cursor 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.
The block above runs the published hermoso npm package on your machine, which is why nothing is pasted and why the tool list costs nothing until a tool is called. If you use the deeplink instead, Cursor performs dynamic client registration against our authorization server and you never hold a key either.
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 Cursor 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 Cursor
Ask for it in ordinary language — these are sentences, not a DSL:
“Turn each bullet in ./docs/changelog.md into a Threads post under 500 characters, post the first three, and save the rest as a queue.”
That walks get_brand → generate_text → post_to_meta (target: "threads") → list_threads_replies. Cursor surfaces each tool call in the composer before it runs, so a publish is a click rather than a side effect.
Cursor on Threads: the part that bites
Working from files makes the 500-character cap easy to design around rather than discover — you can see the copy and the limit at once. Threads is also a separate OAuth grant from Facebook even though it publishes through the same connected Page, so a working Facebook connection does not automatically mean Threads is connected.
Put the config in the project’s .cursor/mcp.json rather than the home directory when a repo should always run against one brand; hermoso auth login is what pins the workspace otherwise.
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 Cursor 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 Cursor, post to: Facebook · Instagram · TikTok · YouTube · X · LinkedIn · Pinterest — or see everything Cursor can publish to.
Post to Threads from: Claude · ChatGPT · Claude Code · Codex · Cline · OpenClaw · Hermes
Frequently asked questions
Can Cursor post to Threads?
Yes, through Hermoso's MCP server. Run npm install -g hermoso && hermoso auth login, then point ~/.cursor/mcp.json at npx -y hermoso mcp. The browser sign-in stores the credential, so no key goes in the file. Cursor then has 681+ 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 Cursor?
Two steps, once each. Run npm install -g hermoso && hermoso auth login, then point ~/.cursor/mcp.json at npx -y hermoso mcp. The browser sign-in stores the credential, so no key goes in the file. Then connect Threads inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Cursor publishes to Threads as an ordinary tool call.
Can Cursor post a carousel to Threads?
Yes — 2 to 20 slides, images and video mixed. Both bounds are Meta’s own published numbers for the Threads API. Cursor calls the same publish tool either way, and a channel that cannot carry a carousel is refused with the real reason attached.
Can Cursor research Threads before it posts?
Yes. search_threads searches public Threads by keyword through the research surface, and search_threads_keyword does the same through your connected account.
Start free — 25 credits at signup and 250+ more to earn, and every feature on every plan.
Start free → See pricing