Post to Threads from Grok Bot

Hermoso is a marketing MCP server: 718+ 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. Grok Bot reaches all of it through one connection. This page is about one slice of that — what Grok Bot can actually do on Threads, and what Threads will not let it do.

Connect Hermoso to Grok Bot

1. Install and sign in.

   npm install -g hermoso && hermoso auth login

   Your browser opens once. Nothing to create and nothing to paste: the credential is stored owner-only in ~/.hermoso/config.json. On a machine with no browser, hermoso auth login --token hmk_… takes a key from Settings → Agents & API keys instead.
2. Add the server. One command, and no key in any file, because hermoso mcp reads the sign-in above:

   grok mcp add hermoso -- npx -y hermoso mcp

   Or write it into ~/.grok/config.toml yourself:

   [mcp_servers.hermoso]
   command = "npx"
   args = ["-y", "hermoso", "mcp"]

3. Or use the hosted endpoint, which installs nothing:

   grok mcp add --transport http hermoso https://app.hermoso.ai/mcp

   x.ai documents what happens next: servers that require OAuth trigger a browser flow on first use, and the tokens are stored under ~/.grok/mcp_credentials.json. You never hold a key either way.
4. Ask a Bot 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.

Hermoso is not affiliated with or endorsed by xAI and does not claim to be. The command shapes, the config.toml keys and the OAuth behaviour above are quoted from x.ai’s own MCP server reference, read on 2026-08-27. Two things worth knowing before you pick a form: --scope project writes .grok/config.toml next to a repo instead of your home directory, which is the right choice when one project should always run against one brand, and /mcps in the TUI opens the MCP tab of the extensions modal if you would rather see the server listed than trust that it registered.

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 Grok Bot 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 Grok Bot

Ask for it in ordinary language — these are sentences, not a DSL:

“Every morning, read my mentions and replies, tell me the question people keep asking, and draft one post under 500 characters answering it.”

That walks get_brand → generate_text → post_to_meta (target: "threads") → list_threads_replies. Approval is Grok Bot’s setting rather than ours, and the shared machine is the reason to think about it: isolation is per user, not per Bot, so anything one Bot connects, every Bot on that machine can reach. What Hermoso enforces underneath, whichever way you set it, is the spend fence. Every campaign object is created paused, and the only switches that arm real money refuse to run without an explicit confirmation flag.

Grok Bot on Threads: the part that bites

Split the loop along the line the tools already draw. Mentions, replies, keyword search and insights have no public effect, so a Bot can do the entire listening job unattended and stop at the draft. The 500-character cap is enforced when the post is queued rather than when it fires, so an over-long batch fails immediately instead of at 9am on a day you are not watching.

On a team plan the server URL may need to go on your MCP allowlist before a Bot can reach it, which is an admin action rather than a failure. And for a long unattended run the hermoso CLI is the cheaper path: the agent shells out per command instead of carrying a 718-tool manifest through every turn of a job that might run for days.

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 Grok Bot 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 Grok Bot, post to: Facebook · Instagram · TikTok · YouTube · X · LinkedIn · Pinterest — or see everything Grok Bot can publish to.

Post to Threads from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Hermes

Frequently asked questions

Can Grok Bot post to Threads?

Yes, through Hermoso's MCP server. Run npm install -g hermoso && hermoso auth login, then grok mcp add hermoso -- npx -y hermoso mcp. The browser sign-in stores the credential, so no key goes in config.toml. Grok Bot then has 718+ 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 Grok Bot?

Two steps, once each. Run npm install -g hermoso && hermoso auth login, then grok mcp add hermoso -- npx -y hermoso mcp. The browser sign-in stores the credential, so no key goes in config.toml. Then connect Threads inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Grok Bot publishes to Threads as an ordinary tool call.

Can Grok Bot 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. Grok Bot calls the same publish tool either way, and a channel that cannot carry a carousel is refused with the real reason attached.

Can Grok Bot 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.