Post, schedule and run ads from Grok Bot

Grok Bot is a team of named agents that share one persistent cloud computer per user, so a job you start on Monday is still there on Thursday with its files, its logins and its history intact. That is a different shape from an editor or a chat window, and it is the shape marketing actually has: a campaign is a thing you come back to. Because each Bot gets a shell, Hermoso installs the same way it does on any terminal.

Hermoso is the marketing half: 718+ tools over one OAuth’d MCP endpoint covering competitor ad research, finished image and video ad generation across 50+ models, publishing and scheduling to ten social channels, and campaign management on Meta, Google Ads, Microsoft Advertising, Reddit Ads, LinkedIn, Pinterest, X Ads, TikTok Ads, Snapchat Ads, ChatGPT Ads and Apple Search Ads. One connection, and Grok Bot has all of it.

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.

Every channel Grok Bot can publish to

Each of these has its own page with that channel’s real caption cap, its real visibility options, what it refuses and why, and a worked example phrased for Grok Bot.

Every one of them queues through one schedule_post calendar with per-channel captions, and list_scheduled reports per-channel outcomes rather than a single green tick — “the job succeeded” and “the post went out” are different questions.

Two channels that are built but not offered

Being straight about this is worth more than a longer list. Two publishing surfaces exist in the codebase and are held back, each waiting on the platform rather than on us:

• Reddit — post_to_reddit is built and reddit_post_stats reads a post back, but Reddit’s Responsible Builder Policy requires explicit written approval before an app may use the Data API, and that ticket has not been granted. The connector is held back rather than offered as an OAuth screen leading to a dead API. Reddit Ads is a different connection and it is live — the full campaign tree, forecasting, targeting search, pixels and lead forms.
• Google Business Profile — post_to_google_business is built, with events, offers and a real call-to-action choice, and so are the listing insights. Google allowlists the Business Profile API per project and the default quota is zero, so every call would 403 for every user. It stays gated until Google grants the project access.

A connector that would hand you a successful OAuth and a dead API is worse than one that is not offered yet, so neither is listed as available.

Three things to type once it is connected

1. Research. “Who are my three closest competitors, and what are their longest-running Meta ads? Tell me which hook keeps repeating.” — walks find_competitors → pull_competitor_ads → mine_angles.
2. Create. “Make me a 9:16 UGC video ad using that hook, with my real product photo and captions burned in.” — walks get_brand → plan_ad → render_ad, and hands back a finished mp4 URL.
3. Ship. “Schedule it to Instagram and TikTok for Tuesday 9am, and build a paused Meta campaign around it targeting the US at $30 a day.” — walks schedule_post → create_meta_campaign → create_meta_ad. The campaign is created paused; nothing spends until you say so.

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.

Beyond publishing

Publishing is the last step, and it is the smallest one. The same connection gives Grok Bot the Meta, Google and LinkedIn ad libraries plus organic TikTok, Instagram, YouTube, Reddit and Threads for research; 50+ image, video, voice and writing models on a single credit meter, with UGC avatars, dubbing, upscaling and native HTML ad formats; and the full campaign tree on eleven paid platforms. There are no per-vendor API keys to hold and no separate app to learn.

See the full tool list, or what a marketing MCP is.

Other clients: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Hermes · any MCP client

Frequently asked questions

Can Grok Bot post to social media?

Yes, once you connect Hermoso's MCP server. Grok Bot can then publish to Facebook, Instagram, Threads, TikTok, YouTube, X, LinkedIn, Pinterest, Bluesky and Telegram — and schedule to all ten from one queue with per-channel captions.

How do I add Hermoso to Grok Bot?

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

Can Grok Bot research my competitors' ads?

Yes. From Grok Bot the Meta, Google and LinkedIn ad libraries are searchable alongside organic TikTok, Instagram, YouTube, Reddit and Threads — ranked by run length, because an ad still running after months is an ad that is paying for itself. It will also tear a competitor down and return a video's voiceover, on-screen text and beat list with timestamps.

Do I need a separate account to use Hermoso in Grok Bot?

No — one Hermoso account, and Grok Bot authenticates against it. The hermoso auth login step signs you in through the browser and stores the credential itself, so there is nothing to paste. The web studio at app.hermoso.ai is the same engine and the same credits.