How to post to Bluesky from Claude Code

Set it up and post, step by step

Prompt to copy once Bluesky is connected: Read CHANGELOG.md, write a Bluesky thread of 4 posts about v2.4 with the release link in a reply under the last one, show it to me, and schedule it for Thursday at 10am.

1. Add PostWire to Claude Code

   In your terminal run claude mcp add --transport http postwire https://postwire.io/api/mcp (add --scope user to have it in every project), then type /mcp in Claude Code and pick postwire to sign in. The sign-in asks for your email and a 6-digit code, which also creates a free PostWire account if you have none: no password and no card.

2. Or install the skill instead

   npx skills add https://postwire.io --skill schedule-posts adds PostWire's scheduling skill to Claude Code instead. It uses your key from the environment: copy it in the dashboard under API & MCP and set POSTWIRE_API_KEY. The skill is a plain file you can read first: schedule-posts/SKILL.md.

3. Create a Bluesky app password

   In Bluesky, open the app passwords page (bsky.app/settings/app-passwords), add one and copy it. It is not your account password, and deleting it in Bluesky disconnects PostWire.

4. Connect Bluesky

   Ask "connect my Bluesky". Claude Code calls create_connect_link and prints a one-hour link; choose Bluesky there and paste your full handle (name.bsky.social or your own domain) and the app password. PostWire signs in to Bluesky with them before it saves anything, so a wrong handle or password is refused on that page, with what to do about it.

5. Ask for the post or the thread

   "Write a Bluesky post about the new CSV import." generate_posts returns a draft and publishes nothing: within 300 characters, conversational, with one or two specific hashtags at most. Ask for a thread, or give it an idea too long for one post, and it returns text (the hook) plus thread (the posts after it, in order); when the idea has a link, the link comes back in first_comment, to go in a reply under the last post.

6. Post now, or schedule it

   Say "post it" and Claude Code calls post_to_social; say "schedule it for Thursday at 10am" and it calls schedule_post, up to 365 days ahead, or with run_at: "next_slot". thread holds up to 9 posts after the first, each a reply to the one before, and first_comment is one more reply under the last one. This is the call:

   {
     "name": "schedule_post",
     "arguments": {
       "platforms": ["bluesky"],
       "per_platform": { "bluesky": {
         "text": "v2.4 took 6 weeks and cut our sync time in half. here is what changed 🧵",
         "thread": [
           "we stopped syncing on every keystroke. saves now batch every 2 seconds.",
           "conflicts get a side-by-side view instead of a silent overwrite.",
           "and dark mode, because you asked 41 times. #buildinpublic"
         ],
         "first_comment": "release notes: https://example.com/changelog/2-4"
       } },
       "run_at": "2026-10-29T10:00:00-05:00"
     }
   }

7. Open the post

   The result carries the post's link (https://bsky.app/profile/…/post/…) and, for a thread, every post's id. If Bluesky refuses a later post of a thread, the earlier ones stay up and the result says which went out and which did not; nothing is posted twice.

"What's scheduled on Bluesky?" calls list_scheduled_posts, and "cancel Thursday's thread" calls cancel_scheduled_post; the same queue is on the dashboard's Queue page. Without Claude Code, the same post is POST /api/post with {"platforms": ["bluesky"], "text": "…"} and your key. Prefer to set it up by hand first? Open the dashboard, connect Bluesky under Accounts and copy your key under API & MCP.