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 Pinterest, and what Pinterest will not let it do.
Connect Hermoso to Grok Bot
- Install and sign in.
Your browser opens once. Nothing to create and nothing to paste: the credential is stored owner-only innpm install -g hermoso && hermoso auth login~/.hermoso/config.json. On a machine with no browser,hermoso auth login --token hmk_…takes a key from Settings → Agents & API keys instead. - Add the server. One command, and no key in any file, because
hermoso mcpreads the sign-in above:
Or write it intogrok mcp add hermoso -- npx -y hermoso mcp~/.grok/config.tomlyourself:[mcp_servers.hermoso] command = "npx" args = ["-y", "hermoso", "mcp"] - Or use the hosted endpoint, which installs nothing:
x.ai documents what happens next: servers that require OAuth trigger a browser flow on first use, and the tokens are stored undergrok mcp add --transport http hermoso https://app.hermoso.ai/mcp~/.grok/mcp_credentials.json. You never hold a key either way. - 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 Pinterest 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 Pinterest tools Grok Bot gets
list_pinterest_boards— the account’s boards, including secret ones, with their ids.create_pinterest_board— makes a new board.post_to_pinterest— creates an image or video Pin on a board you name, with a title, a description, a destination link and alt text.schedule_post— queues the Pin, carryingboardId.list_pinterest_ads_campaigns / pinterest_ads_report— read the paid side.
The limit you need before you plan a Pinterest workflow: this app holds Trial access, and Pinterest refuses Pin creation in production on Trial. Their words, caught on the first real Pin: “Apps with Trial access may not create Pins in production.” Boards and reads do work on Trial — listing boards, creating boards, reading Pins — and Hermoso’s error names the access tier rather than telling you to reconnect, because reconnecting cannot fix it. An upgrade to Standard access is what unblocks Pin creation, and it is pending review. The same tier limits the paid side: on Trial, Pinterest exposes no ad accounts at all.
Pinterest limits worth knowing before you automate anything
| Text | A Pin description is capped at 800 characters and a Pin title at 100. It is enforced when the post is created or queued — refused while you are still there to fix it, rather than silently cut on the way out. |
|---|---|
| Visibility | Public, and the control is the board rather than the Pin. A Pin inherits its board’s public or secret state, so “post it somewhere private” is expressed by choosing a secret board — which is why the board is a required argument rather than a default. |
| Carousel | 2 to 5 images, images only. Both bounds come straight from Pinterest’s own v5 OpenAPI (minItems: 2, maxItems: 5), which is the only machine-readable source Pinterest publishes — their developer site is a client-rendered app that returns nothing to a fetch. There is no multi-video source, so a video slide is refused rather than dropped. |
| Which account | boardId, and it is the only identity field refused at enqueue rather than at publish time: “A Pin has to go on a board — pass boardId. Nothing was scheduled: a Pin on the wrong board is a public mistake, so we never choose one for you.” |
Try it in Grok Bot
Ask for it in ordinary language — these are sentences, not a DSL:
“For every new product this week, generate a vertical Pin image with a title and description and stage it against the right board.”
That walks list_pinterest_boards → plan_ad → generate_image → post_to_pinterest. 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 Pinterest: the part that bites
Do not point a persistent agent at Pin creation and let it keep trying. Pinterest refuses it in production for apps on Trial access, which is an access tier rather than a transient failure, and Hermoso's error names the tier so a Bot can tell the two apart instead of burning a night on retries. Boards read and write, so staging the whole set is real work that survives until Standard access lands.
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 Pinterest before you post
There is no Pinterest ad library, so competitor research on Pinterest is not something Hermoso claims. The creative you would run there is well covered by the rest of the studio — make_template_ad and the image models produce the vertical, text-forward stills the surface rewards.
The paid half
Pinterest Ads tools exist — campaign, ad group and an ad that promotes an existing Pin, everything created paused, and archiving rather than deleting, because Pinterest’s ADS API has no delete verb (organic Pins and boards do delete, through delete_pinterest_pin and delete_pinterest_board; it is the paid objects that can only be archived). But the same Trial-access tier that blocks Pin creation exposes no ad accounts, so ad writes are not usable until Standard access lands. That is the honest state, and it is better in a sentence here than discovered on a deadline.
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 · Threads · TikTok · YouTube · X · LinkedIn — or see everything Grok Bot can publish to.
Post to Pinterest from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Hermes
Frequently asked questions
Can Grok Bot post to Pinterest?
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 Pinterest — and the ones that research the ads already running in your market and render the creative in the first place.
How do I connect Pinterest 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 Pinterest inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Grok Bot publishes to Pinterest as an ordinary tool call.
Can Grok Bot post privately or as a draft to Pinterest?
Visibility on Pinterest lives on the board, not the Pin: a Pin inherits its board’s public or secret state, which is why the board is a required argument rather than a default. Hermoso refuses a visibility Pinterest cannot honour at the moment you ask for it, rather than quietly publishing something weaker.
Can Grok Bot run Pinterest ads as well as posting?
The Pinterest Ads tools exist — campaign, ad group, and an ad promoting a Pin, all created paused — but the same Trial-access tier that blocks Pin creation exposes no ad accounts, so ad writes are not usable until Standard access lands.
Start free — 25 credits at signup and 250+ more to earn, and every feature on every plan.
Start free → See pricing