X Ads
Hermoso is a marketing MCP server. Connect X Ads once and it becomes callable from Claude, ChatGPT, Claude Code, Cursor, Codex, Cline or the CLI — the same connection the web app uses, so nothing is duplicated and nothing is re-authorised per client.
What Hermoso does with X Ads
X (Twitter) campaigns, line items, promoted posts, targeting and reporting.
Advertising: Ad campaigns · Reporting
Driving it from an agent
The X Ads tools an agent can call, by name (17 today):
add_x_ads_targeting create_x_ads_campaign create_x_ads_line_item create_x_ads_promoted_tweet delete_x_ads_object list_x_ads_accounts list_x_ads_campaigns list_x_ads_funding_instruments list_x_ads_line_items list_x_ads_promoted_tweets list_x_ads_targeting set_x_ads_status update_x_ads_campaign update_x_ads_line_item x_ads_geo_search x_ads_report x_ads_targeting_search
Connecting
Open the app, go to Workspace ▸ Connectors and connect X Ads. One authorisation covers the web app, the MCP server and the CLI. See MCP & CLI for the endpoint and the client setup, or every channel we connect to.
Frequently asked questions
Can an AI agent post to X Ads through Hermoso?
Yes. The X Ads surface is exposed over one OAuth'd MCP endpoint, so Claude, ChatGPT, Cursor, Codex, Cline and the CLI can all drive it once the account is connected.
Do I need a separate X Ads connection for the app and for MCP?
No. One authorisation covers the web app, the MCP server and the CLI — it is the same stored connection.