Hermoso is a marketing MCP server: 850+ 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. Cursor reaches all of it through one connection. This page is about one slice of that — what Cursor can actually do on Bluesky, and what Bluesky will not let it do.
Connect Hermoso to Cursor
- Install and sign in.
Your browser opens once. Nothing to create and nothing to paste: the credential is stored owner-only innpm install -g hermoso && hermoso auth login~/.hermoso/config.json. On a machine with no browser,hermoso auth login --token hmk_…takes a key from MCP & CLI → Terminal & API keys instead. - Add it to
~/.cursor/mcp.json(or the project’s.cursor/mcp.json). No key goes in the file, becausehermoso mcpreads the sign-in above:{ "mcpServers": { "hermoso": { "command": "npx", "args": ["-y", "hermoso", "mcp"] } } } - Or use the one-click install from the MCP page. That deeplink installs the hosted URL and leaves authentication to Cursor’s own OAuth flow. Both work, they are just different prerequisites.
- Ask Cursor 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.
The block above runs the published hermoso npm package on your machine, which is why nothing is pasted and why the tool list costs nothing until a tool is called. If you use the deeplink instead, Cursor performs dynamic client registration against our authorization server and you never hold a key either.
Then connect Bluesky itself, once, under Settings → Connectors in Hermoso, with your handle and a Bluesky app password. There is no consent screen: the app password is made in Bluesky’s own settings, and it can be revoked there without touching your real password.
The Bluesky tools Cursor gets
post_to_bluesky— publishes a post as the connected account: up to 300 characters, with up to four images and alt text, or one MP4 video with optional caption tracks. A link with no media gets a preview card, which Hermoso builds because Bluesky does not fetch one.schedule_post— queues it on the calendar every other channel shares, with the 300-character cap checked when it is queued rather than when it fires.list_bluesky_posts— the account’s own recent posts with their AT-URIs and live counts, marking reposts so someone else’s post is never read as yours.bluesky_post_metrics / bluesky_account— likes, reposts, replies, quotes and bookmarks per post, and followers, following and post count for your account or any public one.list_bluesky_convos / read_bluesky_dm / send_bluesky_dm— read and answer direct messages, including message requests from people the account does not follow.manage_bluesky_convo / react_to_bluesky_dm / mark_bluesky_convo_read— accept a request, mute, lock or leave a conversation, react with one emoji, and clear unread counts.delete_bluesky_post— removes a post, after a first call that deletes nothing and reads back what would go.
Bluesky connects with an app password rather than a sign-in screen: create one in Bluesky’s settings and paste it with the handle under Settings → Connectors. Tick direct-message access when you create it, or the DM tools will tell you the password cannot chat, which is a property of the password and not a broken connection. Two more Bluesky rules Hermoso checks before sending: a video needs a confirmed email on the Bluesky account, and a link card and an image cannot share a post. Publishing costs no credits, because Bluesky charges nothing per call.
Bluesky limits worth knowing before you automate anything
| Text | A Bluesky post is capped at 300 characters and, separately, at 3,000 bytes, so an emoji-heavy post can be under 300 characters and still too long. It is enforced when the post is created or queued — refused while you are still there to fix it, rather than silently cut on the way out. |
|---|---|
| Visibility | Public only. A Bluesky post is a public record on the AT Protocol, and there is no unlisted, private or draft form of one. The review happens before the call, never after it. |
| Carousel | 2 to 4 images, images only. Four is Bluesky’s own number, from the AT Protocol lexicon for an image embed, and a fifth is refused rather than dropped. A video is a different embed that carries exactly one clip, and a post has a single embed, so a Bluesky post is images, one video or a link card: one of the three. |
| Which account | None, unless the brand has connected more than one Bluesky account. Then account names which, and several with none named is refused by name rather than guessed. |
Try it in Cursor
Ask for it in ordinary language — these are sentences, not a DSL:
“Post a Bluesky update about this branch’s feature under 300 characters, attach ./docs/img/before.png and after.png with alt text, and link the PR.”
That walks get_brand → generate_image → post_to_bluesky → bluesky_post_metrics. Cursor surfaces each tool call in the composer before it runs, so a publish is a click rather than a side effect.
Cursor on Bluesky: the part that bites
Four images is the ceiling. It comes from Bluesky’s own lexicon, and a fifth is refused rather than dropped. A post also carries one embed, so the images and a card for the PR link cannot both ride: with images attached, the link stays clickable in the text, Hermoso skips the card and tells you. If the before and after matter more than the preview, that is the right trade.
Put the config in the project’s .cursor/mcp.json rather than the home directory when a repo should always run against one brand; hermoso auth login is what pins the workspace otherwise.
Research Bluesky before you post
There is no Bluesky ad library and no Bluesky search in Hermoso, so competitor research there comes down to one honest thing: bluesky_account reads any public account’s followers, following and post count, which is enough to size a competitor and chart it week by week. Everything else in the research surface (the Meta, Google and LinkedIn ad libraries, organic TikTok, Instagram, YouTube, Reddit and Threads) is unaffected.
The paid half
There is no Bluesky ads product in Hermoso, and we do not imply one. Bluesky here is organic: publish, schedule, read, reply and measure. The paid tools cover Meta, Google Ads, Microsoft Advertising, Reddit Ads, LinkedIn, Pinterest, X Ads, TikTok Ads, Snapchat Ads, ChatGPT Ads and Apple Search Ads.
What Cursor 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 — and 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: creating the Bluesky app password and connecting it once. Everything after that is a tool call.
The rest of the matrix
From Cursor, post to: Facebook · Instagram · Threads · TikTok · YouTube · X · LinkedIn · Pinterest · Telegram — or see everything Cursor can publish to.
Post to Bluesky from: Claude · ChatGPT · Claude Code · Codex · Cline · OpenClaw · Grok Bot · Hermes · Gemini CLI · Perplexity · Le Chat
Frequently asked questions
Can Cursor post to Bluesky?
Yes, through Hermoso's MCP server. Run npm install -g hermoso && hermoso auth login, then point ~/.cursor/mcp.json at npx -y hermoso mcp. The browser sign-in stores the credential, so no key goes in the file. Cursor then has 850+ tools, including the ones that publish to Bluesky — and the ones that research the ads already running in your market and render the creative in the first place.
How do I connect Bluesky to Cursor?
Two steps, once each. Run npm install -g hermoso && hermoso auth login, then point ~/.cursor/mcp.json at npx -y hermoso mcp. The browser sign-in stores the credential, so no key goes in the file. Then create an app password in Bluesky's settings (tick direct-message access if you want the DM tools) and paste it with your handle under Settings → Connectors in Hermoso. After that Cursor publishes to Bluesky as an ordinary tool call.
Does Cursor need my Bluesky password?
No, and not your main Bluesky password either. Bluesky connects to Hermoso with an app password, which you create in Bluesky's settings and can revoke there at any time, and Cursor then reaches the account as a tool call. No credential is ever handed to the model.
Can Cursor research Bluesky before it posts?
Only lightly. There is no Bluesky ad library or search in Hermoso, but bluesky_account reads any public account’s followers, following and post count, which is enough to size a competitor.
Start free — 30 credits at signup and 250+ more to earn, and every feature 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