Post, schedule and run ads from Cline

What is Cline?

Cline is an open-source autonomous coding agent that runs inside your editor and loads MCP servers from its own settings file. It takes the standard HTTP MCP server block, which is exactly the block Hermoso publishes for any client that is not one of the named few.

Hermoso is marketing on autopilot: 922+ tools over one MCP endpoint covering competitor ad research, finished image and video ads across 100+ models, publishing and scheduling to eleven social channels, and campaign management on Meta, Google Ads, Microsoft Advertising, Reddit Ads, LinkedIn, Pinterest, X Ads, TikTok Ads, Snapchat Ads, ChatGPT Ads, Apple Search Ads and AppLovin Ads. One connection, and Cline has all of it.

Connect Hermoso to Cline

1. Create an API key. In Hermoso, open the MCP & CLI tab and, under Terminal & API keys, press ＋ Create API key. It looks like hmk_… and carries real spend authority, so treat it like a password.
2. 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>" } }

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

Every channel Cline 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 Cline.

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, because “the job succeeded” and “the post went out” are different questions. A scheduled post lives in Hermoso, so it goes out on time whether or not Cline is still running.

Google Business Profile is the newest channel: Posts with a photo and a button on your Google Search and Maps listing, replies to your reviews, listing edits and the calls, website clicks and direction requests the listing earns. Cline reaches it through the same tools, and schedule_post queues it on the same calendar.

One channel that is built but not offered

Being straight about this is worth more than a longer list. One publishing surface exists in the codebase and is held back, waiting on the platform rather than on us:

• Reddit: organic posting and post stats are built, 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.

A connector that would hand you a successful OAuth and a dead API is worse than one that is not offered yet, so it is not 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.” It runs 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.” It runs 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.” It runs schedule_post → create_meta_campaign → create_meta_ad.

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). 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 yours: linking each account, once. Most channels link through the platform’s own OAuth consent screen in a browser; Bluesky takes an app password and Telegram a bot token, pasted in Hermoso. Everything after that is a tool call.

Cline asks before each tool call by default, which is the behaviour you want on anything that publishes.

What it costs

Adding Hermoso to Cline costs nothing extra: there is one credit meter, and it does not care which client called. A free account starts with 30 credits at signup and 250+ more to earn. Credits are spent only on AI models and Ad Spy research; posting, scheduling, ads management and analytics are free on every channel except X, which bills per call because X charges per API request. Paid plans are $29, $69 and $149 a month for 1,200, 3,000 and 7,000 credits, and every feature is on every plan. hermoso_capabilities gives the exact credit price of any render before it runs.

Troubleshooting

• Calls fail with an authorization error. The key is missing, mistyped or revoked. Create a new one under MCP & CLI → Terminal & API keys.
• A channel is missing. Connect it in Hermoso under Settings → Connectors, then ask Cline to run list_connectors again.
• Cline answers without using Hermoso. Name it in the request: “use Hermoso to …”. That leaves no doubt about which tools should do the job.

Beyond publishing

Publishing is the last step, and it is the smallest one. The same connection gives Cline the Meta, Google and LinkedIn ad libraries plus organic TikTok, Instagram, YouTube, Reddit and Threads for research; 100+ 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 twelve paid platforms. There are no per-vendor API keys to hold and no separate app to learn.

See the full tool list, every agent Hermoso works in, or what a marketing MCP is.

Hermoso in other agents

The same Hermoso account works in every agent below, so your brand, library, schedule and credits follow you between them.

Frequently asked questions

Can Cline post to social media?

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

How do I add Hermoso to Cline?

Create an API key in Hermoso on the MCP & CLI tab, under Terminal & API keys, then point Cline at https://app.hermoso.ai/mcp with an Authorization: Bearer header. 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.

Can Cline generate the video and images too?

Yes, natively rather than by brokering it out. 100+ image, video, voice and writing models sit on one credit meter, and Cline can price a render before it runs it because hermoso_capabilities publishes each model's exact cost. Output is a finished ad, with your real product in the scene and captions and a CTA composited over the render.

Is there a free tier for Cline?

Yes. A free account starts with 30 credits and 250+ more you can earn as you set up and create, and the MCP server itself is free to add to Cline. Paid plans are $29, $69 and $149 a month for 1,200, 3,000 and 7,000 credits. Every feature is on every plan including Free, and the only exception is enterprise SSO.

Is it safe to let Cline post and run ads for me?

Hermoso keeps the steps that cost money or cannot be undone behind gates on its own server, whatever Cline is set to do: every campaign is created paused, spend switches and deletes need an explicit confirmation, and a post only reaches an account you connected and ticked in Hermoso. Cline asks before each tool call by default, which is the behaviour you want on anything that publishes.

Why does Cline use an API key when other clients sign in with OAuth?

Because the block on this page is Hermoso’s generic HTTP configuration, which carries the key as a header, and it is the route we document for Cline. Create the key under MCP & CLI, Terminal & API keys, and revoke it there whenever you like.