Hermoso is a marketing MCP server: 301 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. Cline reaches all of it through one connection. This page is about one slice of that — what Cline can actually do on Pinterest, and what Pinterest will not let it do.
Connect Hermoso to Cline
- Create an API key. In Hermoso, open Settings → Agents & API keys and press ＋ Create API key. It looks like
hmk_…and carries real spend authority, so treat it like a password. - Add an MCP server in Cline’s MCP settings, pointing at the hosted endpoint with your key:
{ "url": "https://app.hermoso.ai/mcp", "headers": { "Authorization": "Bearer <your key>" } } - Ask Cline 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.
This is Hermoso’s generic HTTP MCP block rather than a bespoke Cline integration, and it is worth saying so plainly. What is Cline-specific on our side is the authorization server: it accepts loopback (http://127.0.0.1:PORT/…) redirect URIs precisely so locally installed agents like Cline can complete a registration handshake at all.
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 Cline 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 Cline
Ask for it in ordinary language — these are sentences, not a DSL:
“Create a board for this collection and generate five vertical Pins for it with titles, descriptions and destination links.”
That walks list_pinterest_boards → plan_ad → generate_image → post_to_pinterest. Cline asks before each tool call by default, which is the behaviour you want on anything that publishes.
Cline on Pinterest: the part that bites
An agent that retries on failure will retry forever against Pinterest's Trial-access block, because it is an access tier rather than a transient error — Hermoso's message names the tier for exactly that reason. Boards read and write, so there is real work to do; just do not point a retry loop at Pin creation.
If you run Cline in auto-approve, exclude the publishing and campaign tools — those are the ones with a public or a financial consequence.
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 API has no delete anywhere. 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 Cline 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 Cline, post to: Facebook · Instagram · Threads · TikTok · YouTube · X · LinkedIn — or see everything Cline can publish to.
Post to Pinterest from: Claude · ChatGPT · Claude Code · Cursor · Codex · OpenClaw · Hermes
Frequently asked questions
Can Cline post to Pinterest?
Yes, through Hermoso's MCP server. Create an API key in Hermoso under Settings → Agents & API keys, then add https://app.hermoso.ai/mcp to Cline with an Authorization: Bearer header. Cline then has 301 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 Cline?
Two steps, once each. Create an API key in Hermoso under Settings → Agents & API keys, then add https://app.hermoso.ai/mcp to Cline with an Authorization: Bearer header. Then connect Pinterest inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Cline publishes to Pinterest as an ordinary tool call.
What is the Pinterest caption limit when posting from Cline?
A Pin description is capped at 800 characters and a Pin title at 100. Hermoso enforces it when the post is created or queued, so Cline is told immediately rather than failing later when nobody is watching.
Can Cline research Pinterest before it posts?
There is no Pinterest ad library, and Hermoso does not claim competitor research there. The rest of the research surface — Meta, Google and LinkedIn ad libraries plus organic TikTok, Instagram, YouTube, Reddit and Threads — is unaffected.
Start free — 25 credits at signup and 250+ more to earn, and every feature on every plan.
Start free → See pricing