How to post to X (Twitter) from Claude Code

Set it up and post, step by step

Prompt to copy once X is connected: Read CHANGELOG.md, write an X thread of 4 posts about v2.4 with the link in a reply under it, tell me how many X credits it uses, 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 (and to the other agents on the machine). 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. Connect your X account

   Ask "connect my X account". Claude Code calls create_connect_link and prints a one-hour link that opens X's own sign-in. X shows "Sensitive permissions requested · This app is not affiliated with X", as it does for every outside app: tick I trust this app, then Authorize app. The permission covers posting and uploading media. X needs a paid PostWire plan, and reading your @handle right after connecting uses 1 credit.

4. Ask for the post

   "Write an X post about the new CSV import." generate_posts returns a draft and publishes nothing: one post within 280 characters as X counts them, a first line that stands alone as the hook, one to three short lines of substance, no hashtags and, by default, no link. It writes a thread when you ask for one, and the LinkedIn or Bluesky version of the same news in the same call.

5. Check what it will use

   "How many X credits will that use?" calls get_x_credits with the post's text and thread: it returns the credits for the post or the whole chain, what the plan has left this month and the X posts made today. A post the account cannot cover is not sent.

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 the posts after the first, and reply is one more post under the last one, the usual place for the link. This is the call:

   {
     "name": "schedule_post",
     "arguments": {
       "platforms": ["x"],
       "per_platform": { "x": {
         "text": "v2.4 took 6 weeks and cut our sync time in half. 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.",
           "Dark mode, because you asked 41 times."
         ],
         "reply": "Release notes: https://example.com/changelog/2-4"
       } },
       "run_at": "2026-10-22T10:00:00-05:00"
     }
   }

7. Open the post

   The result carries the post's link (https://x.com/i/web/status/…) and, for a thread, every post's id. If X refuses a later post of a thread, the earlier ones stay up, the result says pending, and PostWire posts the rest by itself without posting anything twice.

"What's scheduled on X?" calls list_scheduled_posts and "cancel Thursday's thread" calls cancel_scheduled_post; the same queue is on the dashboard's Queue page. Prefer to set it up by hand first? Open the dashboard, connect the account under Accounts and copy your key under API & MCP.