Bluesky
Hermoso is a marketing MCP server. Connect Bluesky 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 Bluesky
Post as your account \u2014 300 characters, plus EITHER up to 4 images OR one video, never both (video needs a confirmed email). DMs too: 1000 characters, text only.
Publishing: Post · Schedule · Images · Video · DMs · Delete
Driving it from an agent
The Bluesky tools an agent can call, by name (11 today):
bluesky_account bluesky_post_metrics delete_bluesky_post list_bluesky_convos list_bluesky_posts manage_bluesky_convo mark_bluesky_convo_read post_to_bluesky react_to_bluesky_dm read_bluesky_dm send_bluesky_dm
Connecting
Open the app, go to Workspace ▸ Connectors and connect Bluesky. 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 Bluesky through Hermoso?
Yes. The Bluesky 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 Bluesky 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.