X (Twitter): post & schedule tweets and threads (1Social)

Post to X (Twitter) and schedule X (Twitter) tweets and threads from OpenClaw, Hermes, Claude Code or Codex. Publishes to the user's own X (Twitter) account via the 1Social MCP server (OAuth, no API key), checks the X (Twitter) 280-character limit, thread splitting and image-size rules first, schedules up to 30 days ahead and returns a delivery receipt. Use to post or schedule on X (Twitter), publish a tweet or a thread, plan X (Twitter) content, or check, edit or delete X (Twitter) posts.

X (Twitter) with 1Social

1Social publishes to the user's own X (Twitter) account and reports what actually reached it.

Setup (once)

These steps drive the 1Social MCP server. If tools such as list_accounts are not available, connect it first. Sign-in is OAuth in the browser; there is no API key to store. Ask the user before running these commands — the login step opens a page where they sign in to 1Social themselves.

• OpenClaw: openclaw mcp set 1social '{"url":"https://mcp.1social.dev/mcp","transport":"streamable-http","auth":"oauth"}', then openclaw mcp login 1social. Check with openclaw mcp doctor 1social --probe.
• Hermes: add to ~/.hermes/config.yaml:

  yaml

  mcp_servers:
    1social:
      url: "https://mcp.1social.dev/mcp"
      auth: oauth
  

  then hermes mcp login 1social (on a headless host: hermes mcp login 1social --flow device).
• Claude Code: claude mcp add --transport http 1social https://mcp.1social.dev/mcp
• Any other client: https://1social.dev/mcp lists the setup for each one.

The user needs a 1Social account. New accounts start with a free trial; publishing after it needs a paid plan (https://1social.dev/pricing).

Workflow

1. Find the account. Call list_accounts. It returns the connected channels with their ids, each network's live limits, the plan and the remaining monthly quota. If no X (Twitter) account is connected, tell the user to connect one at https://1social.dev/app — connecting needs a browser and cannot be done from chat. If list_accounts reports a limit that differs from this skill, trust list_accounts.
2. Draft for the network. Write the post to the rules below. A post is a list of segments; each segment is { text, mediaIds? }.
3. Attach media.
   • The user attached a file in chat → put it in media.
   • You have a public https link → put it in mediaUrls.
   • You only have a file on disk (OpenClaw, Hermes, Claude Code, Codex or another CLI agent) → call upload_media and follow the upload steps its description gives, then put the returned publicUrl in mediaUrls. A localhost URL never works. Before that, show the user exactly which files you will upload and wait for a yes: an upload gets a public link at once, and declining the post afterwards does not remove the file.
4. Preview. Call preview_post with the channel ids and the draft. It is free and publishes nothing. Fix every issue it reports and preview again.
5. Confirm with the user. Show the final text, the account it goes to, the media, and when it will go out. Publishing is public and some networks cannot take a post down, so wait for a clear yes.
6. Publish or schedule. Call publish_post. scheduledAt: null publishes now; a UTC ISO-8601 timestamp such as 2026-11-03T07:00:00Z schedules it (in the future, at most 30 days ahead). Convert the user's local time to UTC yourself, and if they name a time without a timezone, ask which one. Set an idempotencyKey (a stable string of 8–128 characters for this draft) so a repeated call cannot publish twice.
7. Report honestly. The result is a per-network receipt. Report each network exactly as returned. unknown means 1Social genuinely could not tell whether the post went out — say so, never call it a success or a failure.

X (Twitter) rules

• Limit: 280 characters per post. Count before previewing; preview_post reports the exact count per segment.
• Threads are native: each segment becomes a reply to the previous one. Split long text into segments of at most 280 characters at sentence boundaries, and number them only if the user wants that.
• Images must be 5 MB or smaller (GIFs up to 15 MB). X does not say "file too large" — it fails with a service error — so check the size first.
• X rejects a post whose text is identical to one the account published recently ("duplicate content"). Change the wording rather than retrying.
• Deleting works: delete_post removes the post from X.

Writing tips

• The first post of a thread carries the reach; make it stand alone.
• One or two hashtags at most.

Posting to other networks too

The same 1Social account can publish one post to Instagram, TikTok, LinkedIn, X, Threads, Facebook Pages, YouTube Shorts and Bluesky at once: list several channel ids from list_accounts. preview_post checks the draft against every selected network.

After publishing

• Check status: list_posts (give a postId for one post). It includes stored engagement metrics where the network reports them.
• Change a scheduled post: update_post. Only works before the post has gone out.
• Unschedule: cancel_post. Use this, not delete_post, for a post that has not been published.
• Delete a published post: delete_post, only after the user confirms. Report per network what actually came down: Instagram, TikTok, Threads and YouTube posts stay live and only the user can remove them.
• A delivery failed: retry_delivery retries one network and spends quota again. It is refused for permanent failures such as a revoked connection — then the user must reconnect at https://1social.dev/app.
• A delivery is unknown: ask the user to look at the network. Only when they tell you whether the post is live, call confirm_delivery with their answer. Never guess, and never retry_delivery with force without asking — it may publish a second copy.