Hermoso is a marketing MCP server: 876+ 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. Paperclip reaches all of it through one connection. This page covers one slice of that: what Paperclip can actually do on X, and what X will not let it do.
Connect Hermoso to Paperclip
- Copy the connector URL.
https://app.hermoso.ai/mcp - Paperclip → Connectors → Connect your own MCP server. Paste the URL. Paperclip asks the server what it needs; Hermoso advertises OAuth, so Paperclip registers a client by itself and opens a browser sign-in.
- Approve on the Hermoso page. Sign in with your Hermoso account and allow access. No key is pasted.
- Set the action permissions. Paperclip lists Hermoso’s tools as read, write or destructive, and each can be Allowed, Ask first or Off. Allow the reads, and keep anything that publishes, schedules or spends on Ask first.
- Ask an agent in Paperclip 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.
Paperclip labels any server outside its reviewed catalog an Unverified server, which in Paperclip’s words is a statement about review, not about whether the connection works. Every Hermoso tool publishes read-only and destructive annotations, so the read, write and destructive split comes from the server rather than from Paperclip guessing at tool names. The steps are quoted from Paperclip’s custom MCP server guide, read on 2026-10-03, and documented rather than run here. Hermoso is not affiliated with or endorsed by Paperclip.
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 Paperclip gets
post_to_x: posts text, an image or a video with alt text, a whole thread, a reply, a quote post or a poll, and can restrict who is allowed to reply.post_x_article: publishes a long-form Article. Write it in Markdown and the headings, lists, quotes, links, code blocks and tables all carry across.edit_x_post: rewrites a post you have already published, inside the hour X allows.schedule_post: queues it on the shared calendar.x_post_metrics: the public counts on a post.x_post_insights: advertiser-grade numbers for the last 28 hours only: impressions, link clicks, profile visits, video views and completion quartiles.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. Length is the posting account’s, not a flat 280. Hermoso reads the account’s own X subscription and sends up to 25,000 characters where Premium allows it, so a long post goes out whole rather than coming back refused, and nothing is ever truncated. That happens to be the cheap shape too: one long post is a single billed X call where the same words split across five posts are five. X Premium also unlocks two things Hermoso publishes for you: a long-form Article, written in Markdown with its headings, lists, quotes, code blocks and tables intact, and an edit to a post you have already published, inside the hour X allows.
X limits worth knowing before you automate anything
| Text | Length is the posting account’s: 280 characters ordinarily, up to 25,000 with X Premium. Hermoso reads the subscription from X, so a long post goes out whole. Nothing is ever truncated. It is enforced when the post is created or queued, so an overlong post is refused while you are still there to fix it instead of being silently cut on the way out. |
|---|---|
| Visibility | Public only. A post on X is public the moment it exists. The API has no draft and no unlisted post. Protected accounts exist, but that is an account-wide setting Hermoso neither reads nor controls, not a per-post choice. |
| Carousel | Refused, by name, for a specific reason. “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 with nothing to swipe to, so a numbered “1/6 · SWIPE” slide deck cannot be published there as intended. The refusal says what to do instead: “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 Paperclip
Ask for it in ordinary language. These are plain sentences, not a DSL:
“Social agent: post one X update about the release, without a link, and report what it cost.”
That walks get_brand → generate_text → post_to_x → x_post_insights_historical. Paperclip puts its own gate in front of every Hermoso call: each action is Allowed, Ask first or Off. Hermoso’s gates sit underneath: campaigns are born paused, and spend switches and deletes need an explicit confirmation.
Paperclip on X: the part that bites
An org of agents that each read X a few times a day adds up, since X charges per request. Keep post_to_x on Ask first, and think twice before Allowing the X read tools for every agent. Length follows the account: 280 characters ordinarily, up to 25,000 on X Premium, and an overlong post is refused rather than cut.
There is a second way to give a Paperclip agent Hermoso, and Paperclip warns that it is different: attaching a server to the agent’s runtime, such as installing Hermoso’s plugin into the Claude Code an agent runs on. That works, but Paperclip’s action permissions and review queue do not sit in front of it. Use the connector when you want Paperclip deciding what an agent may publish.
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 is unaffected: the Meta, Google and LinkedIn ad libraries, and organic TikTok, Instagram, YouTube, Reddit and Threads.
The paid half
X Ads landed in August 2026, so X is now both halves. The X Ads API is a separate product on a separate host with its own OAuth 1.0a signing, which is why it arrived after the rest. Hermoso now builds the whole promoted-post tree on it: campaign, line item (X’s name for an ad group), promoted tweet, targeting, budgets, status and reporting. An X ad promotes a post, so the creative is a post, the same one Hermoso publishes organically. The switch that arms real money refuses to run without an explicit confirmation, exactly as on the other ten platforms. One thing to know before you plan a budget: X grants Ads API access per ad account rather than per app, so there is no OAuth button for it: you add Hermoso’s X user to your ad account at business.x.com → Account access, and it appears in list_x_ads_accounts with the permission level X gave it.
What Paperclip 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 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 Paperclip, post to: Facebook · Instagram · Threads · TikTok · YouTube · LinkedIn · Pinterest · Bluesky · Telegram. Or see everything Paperclip can publish to.
Post to X from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Grok Bot · Hermes · Gemini CLI · Perplexity · Le Chat · Claude Cowork · Perplexity Computer
Frequently asked questions
Can Paperclip post to X?
Yes, through Hermoso's MCP server. In Paperclip, open Connectors, choose Connect your own MCP server, paste https://app.hermoso.ai/mcp and approve the sign-in with your Hermoso account. There is no key to paste. Paperclip then has 876+ tools, including the ones that publish to X, plus 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 Paperclip?
Two steps, once each. In Paperclip, open Connectors, choose Connect your own MCP server, paste https://app.hermoso.ai/mcp and approve the sign-in with your Hermoso account. There is no key to paste. Then connect X inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Paperclip publishes to X as an ordinary tool call.
Does Paperclip need my X password?
No. You connect X to Hermoso once through an OAuth consent screen in a browser, and Paperclip then reaches it as a tool call. Linking an account is the one step that is not headless; nothing after it needs a password, and no credential is ever handed to the model.
Can Paperclip schedule a X post for later?
Yes. schedule_post queues it on one calendar shared with every other channel, with a per-channel caption if the copy should differ, and list_scheduled and cancel_scheduled read and pull it back. X is one of the ten channels that queue.
Can Paperclip post a carousel to X?
No. X’s API attaches up to four media to a post and they render as a grid, with every image visible at once and nothing to swipe to, so a numbered slide deck cannot be published there as intended. Paperclip calls the same publish tool either way, and a channel that cannot carry a carousel is refused with the real reason attached.
What does it cost to post to X from Paperclip?
X is the only connector that bills credits per call, because X charges per API request: roughly $0.015 for a post and $0.200 for a post containing a link, about 13 times more. Your agent is quoted the price before it posts. Plans are $19, $49 and $149 a month for 1,000, 3,000 and 10,000 credits, and every feature is on every plan including Free. The only exception is enterprise SSO.
Start free with 30 credits at signup and 250+ more to earn. Every feature is on every plan. Credits are spent only on AI models and Ad Spy research; posting, scheduling, ads management and analytics are free.
Start free → See pricing