Hermoso is a marketing MCP server: 906+ 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 covers one slice of that: what Grok Bot can actually do on X, and what X will not let it do.
Connect Hermoso to Grok Bot
- Fastest: add the Hermoso Marketing Bot template. Open the template and add it to Grok Bot. It arrives wired to Hermoso but with no key, because templates never carry secrets, so it asks for one: create a key under MCP & CLI → Terminal & API keys and paste it into the Bot’s chat. A key carries real spend authority, so treat it like a password.
- Or sign in from the Bot’s own terminal. Every Bot gets a browser, a filesystem and a shell, so the keyless install works there too:
Thenpm install -g hermoso && hermoso auth loginhermosocommand is then available to the Bot with nothing pasted into a config file. Settings → Plugins is a catalog of pre-built connectors that does not list Hermoso, so the template and the terminal are the ways in today. - Using Grok Build instead? xAI’s terminal coding agent is a separate product with its own setup: see Hermoso in Grok Build.
- 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 Hermoso Marketing Bot template is published by Hermoso; the same steps are in the app under MCP & CLI, on the Grok Bot tab of the agent setup.
Then connect X 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 X tools Grok Bot gets
post_to_x: posts text, an image or a video with alt text, a whole thread, a reply, a quote post or a poll, and can restrict who is allowed to reply.post_x_article: publishes a long-form Article. Write it in Markdown and the headings, lists, quotes, links, code blocks and tables all carry across.edit_x_post: rewrites a post you have already published, inside the hour X allows.schedule_post: queues it on the shared calendar.x_post_metrics: the public counts on a post.x_post_insights: advertiser-grade numbers for the last 28 hours only: impressions, link clicks, profile visits, video views and completion quartiles.x_post_insights_historical: the same numbers over any date range, up to 25 posts at a time. This is the one for “how did last month go”.x_mentions: who is talking about the brand.delete_x_post: removes a post.
X is the only connector that costs money per call, and the numbers are published rather than hidden. Meta, TikTok, LinkedIn, YouTube, Threads and Drive cost nothing per request; X charges us, so those calls bill a small number of credits each. A plain post is priced at $0.015 per request and a post containing a link at $0.200, roughly 13× more. Deletes, reads and the alt-text metadata write each carry their own price, and insights bill per post returned. Link detection deliberately errs toward assuming a link is present, because guessing wrong the other way costs us 13×. The practical consequence: on X, one good post beats five, and your agent is quoted the price before it posts. Length is the posting account’s, not a flat 280. Hermoso reads the account’s own X subscription and sends up to 25,000 characters where Premium allows it, so a long post goes out whole rather than coming back refused, and nothing is ever truncated. That happens to be the cheap shape too: one long post is a single billed X call where the same words split across five posts are five. X Premium also unlocks two things Hermoso publishes for you: a long-form Article, written in Markdown with its headings, lists, quotes, code blocks and tables intact, and an edit to a post you have already published, inside the hour X allows.
X limits worth knowing before you automate anything
| Text | Length is the posting account’s: 280 characters ordinarily, up to 25,000 with X Premium. Hermoso reads the subscription from X, so a long post goes out whole. Nothing is ever truncated. 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. A post on X is public the moment it exists. The API has no draft and no unlisted post. Protected accounts exist, but that is an account-wide setting Hermoso neither reads nor controls, not a per-post choice. |
| Carousel | Refused, by name, for a specific reason. “X has no swipeable carousel.” Its API attaches up to 4 media to a post and they render as a grid, every image visible at once with nothing to swipe to, so a numbered “1/6 · SWIPE” slide deck cannot be published there as intended. The refusal says what to do instead: “Post the single strongest slide to X, or drop X from this post.” A deck that instructs the reader to swipe, published as a grid, is worse than not publishing it. |
| Which account | None. X publishes to the connected account. |
Try it in Grok Bot
Ask for it in ordinary language. These are plain sentences, not a DSL:
“Post at most one update a day about what shipped, under 280 characters, and only include a link when there is genuinely something to link to.”
That walks get_brand → generate_text → post_to_x → x_post_insights_historical. 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.
Grok Bot on X: the part that bites
This is the channel where an always-on agent costs real money rather than context. Posts, deletes, reads and the alt-text write are each billed requests, insights bill per post returned, and a post carrying a link is priced at roughly 13 times a plain one. Link detection deliberately errs toward assuming a link is present, so a job that hopes to be cheap sometimes is not a budget. Put the cap in the instruction.
For a long unattended run the hermoso CLI is the cheaper path: the agent shells out per command instead of carrying an 906+ tool manifest through every turn of a job that might run for days.
Research X before you post
There is no X ad library to search. X research here is your own account: mentions, post metrics and the historical advertiser numbers. Everything else in the research surface is unaffected: the Meta, Google and LinkedIn ad libraries, and organic TikTok, Instagram, YouTube, Reddit and Threads.
The paid half
X Ads landed in August 2026, so X is now both halves. The X Ads API is a separate product on a separate host with its own OAuth 1.0a signing, which is why it arrived after the rest. Hermoso now builds the whole promoted-post tree on it: campaign, line item (X’s name for an ad group), promoted tweet, targeting, budgets, status and reporting. An X ad promotes a post, so the creative is a post, the same one Hermoso publishes organically. The switch that arms real money refuses to run without an explicit confirmation, exactly as on the other eleven platforms. One thing to know before you plan a budget: X grants Ads API access per ad account rather than per app, so there is no OAuth button for it: you add Hermoso’s X user to your ad account at business.x.com → Account access, and it appears in list_x_ads_accounts with the permission level X gave it.
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). 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 · Threads · TikTok · YouTube · LinkedIn · Pinterest · Bluesky · Telegram. Or see everything Grok Bot can publish to.
Post to X from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Hermes · Gemini CLI · Perplexity · Le Chat · Claude Cowork · Perplexity Computer · Paperclip
Frequently asked questions
Can Grok Bot post to X?
Yes, through Hermoso's MCP server. Add the Hermoso Marketing Bot template from x.ai/bot/THQqogUKuhn1whWU0hrmb, which arrives wired to Hermoso and asks for an API key you create under MCP & CLI, Terminal & API keys. Or run npm install -g hermoso && hermoso auth login in the Bot's own terminal, which stores the credential with nothing pasted. Grok Bot then has 906+ tools, including the ones that publish to X, plus the ones that research the ads already running in your market and render the creative in the first place.
How do I connect X to Grok Bot?
Two steps, once each. Add the Hermoso Marketing Bot template from x.ai/bot/THQqogUKuhn1whWU0hrmb, which arrives wired to Hermoso and asks for an API key you create under MCP & CLI, Terminal & API keys. Or run npm install -g hermoso && hermoso auth login in the Bot's own terminal, which stores the credential with nothing pasted. Then connect X inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Grok Bot publishes to X as an ordinary tool call.
What is the X caption limit when posting from Grok Bot?
That depends on the account, and Hermoso checks rather than guessing. An ordinary X account is capped at 280 characters; one with X Premium goes up to 25,000. Hermoso reads the subscription from X and sends the post, so a long post goes out whole, and nothing is ever truncated. On a Premium account one long post usually reads better than a thread and costs less, because it is a single billed X call where five parts are five. Premium also unlocks long-form Articles, written in Markdown, and an edit to a post already published inside the hour X allows. Hermoso enforces it when the post is created or queued, so Grok Bot is told immediately rather than failing later when nobody is watching.
Can Grok Bot run X ads as well as posting?
Yes, since August 2026. X Ads runs on a separate host with its own OAuth 1.0a signing, and Hermoso builds the whole tree on it: campaign, line item, promoted tweet, targeting, budgets, status and reporting. X grants Ads API access per ad account rather than per app, so there is no OAuth button for it: you add Hermoso’s X user to your ad account at business.x.com → Account access.
Can Grok Bot post privately or as a draft to X?
No. A post on X is public the moment it exists; the API has no draft and no unlisted post. Hermoso refuses a visibility X cannot honour at the moment you ask for it, rather than quietly publishing something weaker.
Can Grok Bot research X before it posts?
Not through an ad library, because X publishes none. What Hermoso reads on X is your own account: post metrics, advertiser-grade insights over any date range, and brand mentions.
Related
The long version, with the setup and what it did in practice: run your marketing with a Grok bot and autonomous marketing with a Grok bot.
The same bot on other channels: Instagram, TikTok, YouTube, Facebook, LinkedIn, Threads and Pinterest.
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