How to Post to Bluesky with Claude (No AT Protocol Setup)
How to post to Bluesky with Claude using the Blotato MCP server. Connect once, then publish posts from a single prompt.
To post to Bluesky with Claude, you connect the Blotato MCP server to Claude once, then type a prompt like “post this to my Bluesky.” Claude calls Blotato, Blotato publishes to your Bluesky account, and you skip the AT Protocol complexity, credential management, and per-platform OAuth juggling entirely. I’m the founder, so take this with whatever grain of salt feels right: this is the same setup I use to run my own accounts, 2.4M+ followers and 500M+ views across nine platforms.
Most guides for Bluesky either walk you through the AT Protocol directly (which means handling credentials and API tokens yourself) or browser automation (which breaks the moment Bluesky changes a button). The Blotato MCP path is neither. One connection lets Claude publish to Bluesky plus eight other platforms. Once posting works, you can run the whole content engine this way, drafting, grading, and scheduling all from Claude.
What You Need Before You Start
Get these three things in place before Claude can publish a single Bluesky post:
- A paid Blotato plan. Blotato’s API is what the MCP server runs on, and the API ships with every paid plan: Starter $29/mo, Creator $97/mo, Agency $499/mo. The free trial leaves API and MCP access out.
- A Bluesky account linked in Blotato. Add it in Settings first, before you ever open Claude.
- A Bluesky personal account, since that is the account type Blotato supports here.
- Claude Desktop or Claude Code. The same MCP server drives both, so pick whichever you already use.
How to Post to Bluesky with Claude
The setup runs from connecting your account to firing the prompt that publishes your post. Four steps, in order.
Step 1: Connect Your Bluesky Account in Blotato
Log into Blotato, open Settings, and click “Login with Bluesky” under your social platforms. Then manually type your Bluesky handle without the leading @, so use yourname.bsky.social, not @yourname.bsky.social. Type it out instead of copy-pasting, since pasting can slip in invisible characters that break the connection. Blotato handles the authentication, so Claude can publish later without you passing credentials around.
Step 2: Add the Blotato MCP Server to Claude
Connect the Blotato MCP server to Claude. On Claude Desktop, open Customize, head to Connectors, and register a custom connector pointing at https://mcp.blotato.com/mcp. On Claude Code, run the command below, then /mcp, choose Blotato > Authenticate, approve access, and restart Claude Code so the server loads.
claude mcp add --transport http Blotato https://mcp.blotato.com/mcpThere is no key to paste, the connection rides on your logged-in browser session. The full walkthrough lives in Blotato’s MCP setup guide. When the /mcp panel lists Blotato as connected, Claude is cleared to post for you.
Step 3: Confirm the Connection
Ask Claude to “list my Blotato accounts.” Claude runs the blotato_list_accounts tool and returns every platform you have connected, including Bluesky, with each account ID. Seeing your Bluesky account in that list confirms Claude can publish to it. If Bluesky is missing, go back to Step 1 and check that the connection saved.
Step 4: Write the Prompt That Posts to Bluesky
Tell Claude what to publish in plain language. A prompt like “Post this to my Bluesky: Just launched a new feature with Claude Code” is enough. Claude calls blotato_create_post with your account ID, the bluesky platform, and your post text. Bluesky caps posts at 300 characters, so ask Claude to keep it under the limit if your text runs long. You can attach up to 4 images by including public image URLs in your prompt, and if your idea needs more room than one post, ask Claude for a thread: Blotato chains the replies for you through the same call. Once the status comes back as published, your post is live on your Bluesky timeline.
The published post looks like this on the Bluesky timeline, image attached and link in place:
Step 5: Schedule the Post for Later (Optional)
To queue a Bluesky post rather than send it now, attach a time to the prompt. Say “schedule this for tomorrow at 9am” and Claude hands a scheduledTime to Blotato. Prefer “drop it in my next free slot” and Blotato slots it into the next open time on your calendar. Anything you queue lives in Blotato, and you edit it the same way you made it: tell Claude “move the Friday noon Bluesky post to 1pm” and it reschedules without you touching the calendar.
Want Claude posting to Bluesky today? Start with Blotato, and the MCP connection takes about two minutes.
Why Use Blotato’s MCP Instead of the AT Protocol or Browser Automation?
The Blotato MCP server skips the painful parts most people hit when they try to get Claude posting to Bluesky. The AT Protocol requires you to handle credentials directly, manage app passwords, and understand the protocol’s object structure, all complexity you don’t need if you just want to post. The API itself is free, and the full Bluesky API cost breakdown covers the rate-limit points math if you’re weighing the DIY route. Browser automation, where Claude clicks through Bluesky’s web UI, breaks every time the interface changes.
Generic agent toolkits come with a different tax. Each platform needs its own OAuth or credential setup, so Bluesky, TikTok, and LinkedIn become three separate chores instead of one. Blotato authenticates each account once on its own side, then surfaces all nine networks (Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Threads, Pinterest, Bluesky) behind one MCP connection. So the same prompt that ships a Bluesky post can send it everywhere else too, no rewriting.
Bluesky is not an afterthought in my own stack either. I built an automation that listens for an email with a rough idea, has AI expand it into a long form thread, and queues it to X, Threads, and Bluesky at a scheduled time, posting into the same Blotato account where you linked Bluesky in Step 1. Since Bluesky, X, and Threads are all text-first, the same short post usually works across all three, and you can wire them up the same way with how to post to X with Claude Code and how to post to Threads with Claude.
If you want the deeper technical reason, Bluesky’s API get-started guide shows the session and posting steps Blotato handles for you. And once you’re posting, how to automate social media with Claude Cowork shows how to feed the whole content pipeline through Claude.
Common Mistakes to Avoid
Four things catch most people out the first time they wire this up:
- Trying this during the trial. API and MCP access both require a paid plan. Generating an API key in Settings ends the trial early and drops you straight onto paid Starter.
- Skipping the account connection. Claude cannot post to a Bluesky account that is not connected in Blotato first. Ask Claude to “list my Blotato accounts” and confirm Bluesky is in the list.
- Copy-pasting your handle when connecting. Pasting your Bluesky handle can bring in invisible characters that break the connection, and leaving the @ in front is the other common cause. Type the handle manually without the @, like
yourname.bsky.social. - Posting a video without verifying your email. Blotato can post videos to Bluesky, but Bluesky requires a verified email on your account before it allows video posts. Verify your email in Bluesky first.
- Forgetting the 300-character limit. Bluesky posts are capped at 300 characters. If Claude tries a longer post, it will fail or trim it. Keep prompts concise or ask Claude to check the length first.
Conclusion
Posting to Bluesky with Claude comes down to one connection and one prompt. Connect your Bluesky account in Blotato, add the MCP server to Claude Desktop or Claude Code, then tell Claude what to publish or schedule. No AT Protocol credentials, no browser automation, no per-platform OAuth. Try Blotato and let Claude run your Bluesky posting.
How to Post to Bluesky with Claude FAQs
Can you post to Bluesky with Claude?
Yes. Claude cannot post to Bluesky on its own, but it can through the Blotato MCP server. Once Blotato is connected to Claude and your Bluesky account is linked inside Blotato, a prompt like “post this to my Bluesky” tells Claude to publish through Blotato’s API. The workflow runs in either Claude Desktop or Claude Code.
How do I connect Claude to Bluesky?
Connecting Claude to Bluesky takes two places. Link your Bluesky account in Blotato under Settings, then point Claude at Blotato’s MCP server (https://mcp.blotato.com/mcp), as a custom connector in Desktop or one claude mcp add line in Code. Approve the access request and Claude can post to that account.
Do you need the AT Protocol to post to Bluesky with Claude?
No. Blotato handles the AT Protocol authentication on its side, so you never set up credentials, manage app passwords, or work with the protocol directly yourself. You connect your Bluesky account once in Blotato, and Claude publishes through Blotato instead of talking to AT Protocol directly.
Can Claude schedule Bluesky posts for later?
Yes. Give Claude a time and it schedules through Blotato rather than publishing immediately. Name a specific slot or let Blotato pick your next open one. The queued Bluesky post stays in Blotato, so you can move or cancel it before it goes out.
What is the character limit for Bluesky posts?
Bluesky posts are capped at 300 characters. Claude will trim longer posts or ask you to shorten them. Keep prompts concise so Claude publishes without hitting the limit.