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 X, and what X 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 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 Cline gets
post_to_x— posts text, an image or a video with alt text, a whole thread, a reply, or a poll — and can restrict who is allowed to reply.schedule_post— queues it on the shared calendar.x_post_metrics— the public counts on a post.x_post_insights— advertiser-grade numbers — impressions, link clicks, profile visits, video views and completion quartiles — for the last 28 hours only.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. Over-length copy is also refused, never truncated — 280 characters, with the overage counted for you and a suggestion to split it into a thread.
X limits worth knowing before you automate anything
| Text | An X post is capped at 280 characters, and over-length copy is refused rather than truncated. 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 only. A post on X is public the moment it exists — there is no draft and no unlisted post in the API. Protected accounts exist, but that is an account-wide setting Hermoso neither reads nor controls, not a per-post choice. |
| Carousel | Refused, by name, and for a reason that is specific rather than generic: “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, nothing to swipe to — so a numbered ‘1/6 · SWIPE’ slide deck cannot be published there as intended. 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 Cline
Ask for it in ordinary language — these are sentences, not a DSL:
“Draft an X post under 280 characters about this fix, price it, and wait for my approval before posting.”
That walks get_brand → generate_text → post_to_x → x_post_insights_historical. Cline asks before each tool call by default, which is the behaviour you want on anything that publishes.
Cline on X: the part that bites
Keep X out of auto-approve on cost grounds alone. Every post, reply, delete and read is a billed request; insights bill per post returned; a link multiplies a post's price by roughly 13. Hermoso quotes the cost first, which only helps if something is there to read it.
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 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 — Meta, Google and LinkedIn ad libraries, organic TikTok, Instagram, YouTube, Reddit and Threads — is unaffected.
The paid half
X Ads do not exist in Hermoso, and we name that rather than leaving it ambiguous. The X Ads API is a separate product on a separate host with its own OAuth 1.0a signing and its own approval process. X is an organic channel here: Hermoso posts, threads, replies, deletes and reads post metrics, and does not create or manage X ad campaigns.
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 · LinkedIn · Pinterest — or see everything Cline can publish to.
Post to X from: Claude · ChatGPT · Claude Code · Cursor · Codex · OpenClaw · Hermes
Frequently asked questions
Can Cline post to X?
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 X — and 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 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 X inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Cline publishes to X as an ordinary tool call.
Can Cline 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 Cline research X before it posts?
Not through an ad library — X publishes none. What Hermoso reads on X is your own account: post metrics, advertiser-grade insights over any date range, and brand mentions.
Start free — 25 credits at signup and 250+ more to earn, and every feature on every plan.
Start free → See pricing