Post to Instagram 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 Instagram, and what Instagram 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 Instagram 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 Instagram tools Grok Bot gets

• post_to_meta — publishes to Instagram with target: "instagram". Instagram is a visual channel and the API agrees — a post needs an image or a video.
• schedule_post — queues it on the shared calendar, with a per-channel caption if the copy should differ from your Facebook or LinkedIn version.
• list_meta_comments / reply_to_meta_comment / moderate_meta_comment — read, reply and moderate under a post.
• meta_page_insights / meta_post_insights — reach, impressions, saves and engagement, per account and per post.
• search_instagram — keyword search across public Instagram Reels — research, not publishing.

Two Instagram facts worth knowing before you automate anything. There is no native Instagram scheduling in Meta’s API, so a schedule is Hermoso’s queue rather than Instagram’s, and passing Facebook’s scheduleAt for Instagram is refused rather than silently posted now. And an Instagram caption cannot be edited once the post is live: the only thing Meta lets you change on a published post is whether comments are enabled. Deleting one is supported — manage_meta_post removes ordinary posts, Stories, Reels and entire carousel albums, though never a single card out of an album.

Instagram limits worth knowing before you automate anything

Try it in Grok Bot

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

“Build me a 5-slide carousel from this week's product shots and a 9:16 video of the best angle, then stop and show me both before anything goes out.”

That walks search_instagram → plan_ad → render_ad → post_to_meta (target: "instagram"). 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 Instagram: the part that bites

Instagram is the one channel where the CAPTION is final: Meta lets you change nothing on a live post except whether comments are enabled. Taking it down is fine — manage_meta_post deletes posts, Stories, Reels and whole albums — so the thing worth a second look is the words, not the decision to publish. Everything upstream is reversible anyway: research, planning, rendering, captioning. Write the job so the caption gets read one thing it is not allowed to do alone.

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 Instagram before you post

search_meta_ads covers Instagram placements as well as Facebook — it is one library. For organic, search_instagram searches public Reels by keyword, which is the surface where the format actually moves; profile and hashtag pulls go through fetch_social_data and search_instagram_hashtag.

The paid half

Instagram placements are bought through the same Meta campaign tree as Facebook: create_meta_campaign → create_meta_adset → create_meta_ad, with placements selectable per platform and position. Objects are created paused with no caller override, preview_meta_ad shows the real rendered ad per placement before you spend, and meta_insights breaks results down by age, gender, placement and country — which is the input to the next creative, not just a total.

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

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

Frequently asked questions

Can Grok Bot post to Instagram?

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 Instagram — and the ones that research the ads already running in your market and render the creative in the first place.

How do I connect Instagram 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 Instagram inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Grok Bot publishes to Instagram as an ordinary tool call.

What is the Instagram caption limit when posting from Grok Bot?

An Instagram caption is capped at 2,200 characters, and the limit is enforced when the post is queued rather than when it fires. 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 Instagram ads as well as posting?

Yes, through the Meta campaign tree — Instagram placements are selected inside a Meta ad set. Objects are created paused, and preview_meta_ad renders the real ad per placement before you spend.