Post, schedule and run ads from Hermes

What is Hermes?

Hermes is an agent runtime that loads MCP servers from ~/.hermes/config.yaml. It starts them as local processes, so it takes the keyless route: sign in once from the terminal and the same 922+ tools appear, with no secret in the file.

Two ways in. This page uses a local server and the terminal sign-in. Hermes can also sign in to the hosted endpoint with OAuth 2.1, which the Hermes connect guide covers, along with Hermoso’s Agent Skills.

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 Hermes has all of it.

Connect Hermoso to Hermes

1. Install and sign in.

   npm install -g hermoso && hermoso auth login

   Your browser opens once. Nothing to create and nothing to paste: the credential is stored owner-only in ~/.hermoso/config.json. On a machine with no browser, hermoso auth login --token hmk_… takes a key from MCP & CLI → Terminal & API keys instead.
2. Add it to ~/.hermes/config.yaml. mcp_servers is a top-level key, not nested under mcp, and no key goes in the file because hermoso mcp reads the sign-in above:

   mcp_servers:
     hermoso:
       command: "npx"
       args: ["-y", "hermoso", "mcp"]

3. Ask Hermes 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 the makers of Hermes and does not claim to be. The shape above is quoted from the project's own MCP reference in NousResearch/hermes-agent, read on 2026-08-23; it is documented rather than run here, which is why it is the published file shape and not a bespoke install command.

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

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

Approval behaviour is yours to configure. Hermoso’s own guarantees do not depend on it: campaigns are born paused, spend switches are confirm-gated, and no generation call runs without a verified account behind it.

What it costs

Adding Hermoso to Hermes 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

• A local server prints help and exits. The arguments are missing the trailing mcp. npx -y hermoso on its own prints help; npx -y hermoso mcp starts the server.
• There is no browser on that machine. Create a key under MCP & CLI → Terminal & API keys and run npx -y hermoso auth login --token hmk_… instead.
• A channel is missing. Connect it in Hermoso under Settings → Connectors, then ask Hermes to run list_connectors again.
• Hermes 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 Hermes 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 Hermes post to social media?

Yes, once you connect Hermoso's MCP server. Hermes 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 Hermes?

Run npm install -g hermoso && hermoso auth login, then add hermoso under the top-level mcp_servers key in ~/.hermes/config.yaml with command "npx" and args ["-y", "hermoso", "mcp"]. The browser sign-in stores the credential, so no key goes in the file. Hermoso is not affiliated with or endorsed by the makers of Hermes and does not claim to be. The shape above is quoted from the project's own MCP reference in NousResearch/hermes-agent, read on 2026-08-23; it is documented rather than run here, which is why it is the published file shape and not a bespoke install command.

Can Hermes 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 Hermes 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 Hermes?

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 Hermes. 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 Hermes post and run ads for me?

Hermoso keeps the steps that cost money or cannot be undone behind gates on its own server, whatever Hermes 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. Approval behaviour is yours to configure. Hermoso’s own guarantees do not depend on it: campaigns are born paused, spend switches are confirm-gated, and no generation call runs without a verified account behind it.

Is this the same as Hermes Agent by Nous Research?

Yes. Hermes Agent is the open-source agent runtime from Nous Research, and the config shape on this page is quoted from its own MCP reference in NousResearch/hermes-agent.