X (Twitter) MCP server: let Claude or any agent post tweets and threads

Set it up and post, step by step

1. Add PostWire's MCP server to your agent

   In Claude, open PostWire in the connector directory and press Connect. Anywhere else, add the remote server https://postwire.io/api/mcp (Streamable HTTP; OAuth sign-in or an API key) — in Claude Code: claude mcp add --transport http postwire https://postwire.io/api/mcp. Cursor, VS Code, Windsurf, Codex and Gemini CLI configs: MCP client configs.

2. Sign in with your email

   The first time the agent uses a PostWire tool, a sign-in window asks for your email and a 6-digit code; that also creates a free PostWire account if you have none. No password and no card. Agents that cannot do OAuth send an API key instead (dashboard → API & MCP → Copy key).

3. Connect your X account

   Ask "connect my X account". create_connect_link gives you 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; PostWire never likes, follows, replies to other people or sends messages. X needs a paid PostWire plan, and reading your @handle right after connecting uses 1 credit.

4. Let PostWire write the post

   "Write an X post about our new CSV import." generate_posts returns a draft and publishes nothing. X's draft is one post within 280 characters as X counts them, with 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 only when you ask for one.

5. Ask what it will use

   get_x_credits with the post's text (and its thread) returns how many credits the post or the whole chain would use, what the plan has left this month and how many X posts the account has made today. An agent running on its own can check before every post.

6. Publish, or schedule it

   After you approve, the agent calls post_to_social (or schedule_post with a run_at time up to 365 days ahead, or "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:

   {
     "name": "post_to_social",
     "arguments": {
       "platforms": ["x"],
       "per_platform": {
         "x": {
           "text": "We rebuilt our CSV import three times before it worked. Here is what each attempt got wrong.",
           "thread": [
             "Attempt 1 trusted the header row. Half the files we got had none.",
             "Attempt 2 guessed the columns. It guessed dates as phone numbers.",
             "Attempt 3 shows you the first five rows and asks. That one shipped."
           ],
           "reply": "The full write-up: https://example.com/csv-import"
         }
       }
     }
   }

7. Open the post

   The result carries the post's link (https://x.com/i/web/status/…) and, for a thread, thread.tweets with every post's id, thread_url and thread.status. get_post_status returns them again later; list_scheduled_posts shows what is queued and cancel_scheduled_post removes one before it goes out.

An image or a video from your phone or laptop gets there through create_upload_link: a 24-hour page where you pick the file, then get_uploaded_file returns its media_url. The same post from your own code: POST /api/post with {"platforms": ["x"], "text": "…"} and your API key, or the PostWire node in n8n. Prefer to set it up by hand first? Open the dashboard, connect the account under Accounts and copy your key under API & MCP.