Post to Threads from Cursor

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. 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

1. 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.
2. Add it to ~/.cursor/mcp.json (or the project’s .cursor/mcp.json):

   { "mcpServers": { "hermoso": {
       "url": "https://app.hermoso.ai/mcp",
       "headers": { "Authorization": "Bearer <your key>" }
   } } }

3. Or use the one-click install from the MCP page. That deeplink installs the bare URL and leaves authentication to Cursor’s own OAuth flow instead of a pasted key — both work, they are just different prerequisites.
4. 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 config above is the path Hermoso publishes and tests. If you use the deeplink instead, Cursor performs dynamic client registration against our authorization server and you never hold a key.

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 with target: "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

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 several brands share a machine — the key is what pins the workspace.

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 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. Create an API key in Hermoso under Settings → Agents & API keys, then add https://app.hermoso.ai/mcp to Cursor with an Authorization: Bearer header. Cursor 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 Cursor?

Two steps, once each. Create an API key in Hermoso under Settings → Agents & API keys, then add https://app.hermoso.ai/mcp to Cursor with an Authorization: Bearer header. 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.