Post, schedule and run ads from Manus

What is Manus?

Manus is a general AI agent that finishes multi-step work on its own, in a sandboxed virtual computer with internet access, a persistent file system and the ability to install software. It takes custom MCP servers alongside its prebuilt connectors, so Hermoso becomes a set of tools any Manus task can call.

Manus or Cue? Cue is Manus’s newer app of agents that each hold a responsibility and run routines. It has no documented custom MCP option yet, so this page covers Manus only.

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

Connect Hermoso to Manus

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 a custom MCP server in Manus. Manus’s docs put it under Settings → Integrations → Custom MCP Servers → Add Server; if your settings show Connectors instead, the custom MCP option is there. Name it Hermoso, set the server URL to https://app.hermoso.ai/mcp, and give your key as the Bearer token.
3. Test the connection when Manus offers it, then start a task that names Hermoso.
4. Ask Manus 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.

Manus documents custom servers with an API key or Bearer token, so the key route is the one we publish here; we have not found Manus documentation of an OAuth sign-in for a custom server. A Hermoso key carries real spend authority, so revoke it under MCP & CLI the day you stop using Manus. The steps are quoted from Manus’s custom MCP documentation, read on 2026-10-03, and documented rather than run here. Hermoso is not affiliated with or endorsed by Manus.

Every channel Manus can publish to

Each channel links to its Hermoso page, with that channel’s real caption cap, visibility options and what it refuses. Manus reaches all of them through the same tools as every other agent.

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 Manus is still running.

Two channels that are built but not offered

Being straight about this is worth more than a longer list. Two publishing surfaces exist in the codebase and are held back, each 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.
• Google Business Profile: post_to_google_business is built, with events, offers and a real call-to-action choice, and so are the listing insights. Google allowlists the Business Profile API per project and the default quota is zero, so every call would 403 for every user. It stays gated until Google grants the project access.

A connector that would hand you a successful OAuth and a dead API is worse than one that is not offered yet, so neither is 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 Manus 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.

Manus works through a task on its own, so put the review step in the request: “show me the caption and wait for my yes before posting.” Hermoso’s gates hold underneath: campaigns are born paused, and spend switches and deletes need an explicit confirmation.

What it costs

Adding Hermoso to Manus 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 $19, $49 and $149 a month for 1,000, 3,000 and 10,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 Manus to run list_connectors again.
• Manus answers without using Hermoso. Name it in the request: “use Hermoso to …”. That leaves no doubt about which tools should do the job.
• Manus says the server rejected the request. The key is missing, mistyped or revoked. Create a new one under MCP & CLI, Terminal & API keys, and paste it as the Bearer token.

Beyond publishing

Publishing is the last step, and it is the smallest one. The same connection gives Manus 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 eleven 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 Manus post to social media?

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

How do I add Hermoso to Manus?

Create an API key in Hermoso on the MCP & CLI tab, under Terminal & API keys, then add https://app.hermoso.ai/mcp in Manus as a custom MCP server with that key as the Bearer token. Manus documents custom servers with an API key or Bearer token, so the key route is the one we publish here; we have not found Manus documentation of an OAuth sign-in for a custom server. A Hermoso key carries real spend authority, so revoke it under MCP & CLI the day you stop using Manus. The steps are quoted from Manus’s custom MCP documentation, read on 2026-10-03, and documented rather than run here. Hermoso is not affiliated with or endorsed by Manus.

Can Manus research my competitors' ads?

Yes. From Manus the Meta, Google and LinkedIn ad libraries are searchable alongside organic TikTok, Instagram, YouTube, Reddit and Threads, ranked by run length, because an ad still running after months is an ad that is paying for itself. It will also tear a competitor down and return a video's voiceover, on-screen text and beat list with timestamps.

Do I need a separate account to use Hermoso in Manus?

No. One Hermoso account is enough, and Manus authenticates against it. You create an API key once on the MCP & CLI tab, under Terminal & API keys and paste it into the config. The web studio at app.hermoso.ai is the same engine and the same credits.

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

Hermoso keeps the steps that cost money or cannot be undone behind gates on its own server, whatever Manus 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. Manus works through a task on its own, so put the review step in the request: “show me the caption and wait for my yes before posting.” Hermoso’s gates hold underneath: campaigns are born paused, and spend switches and deletes need an explicit confirmation.

Is Hermoso in the Manus connector directory?

No. Hermoso connects to Manus as a custom MCP server, which Manus supports alongside its prebuilt connectors. You add the URL and your Hermoso key once in Manus’s settings.