Draft, review and post from Claude Code or Cursor

Go from an idea to an approved, scheduled X thread without leaving your assistant.

• ✓ An active ThreadMaster subscription, a connected X account, and an API key from Settings → Developer API.
• ✓ Claude Code or Cursor with remote MCP support; choose threads:read, threads:write, publish:read and publish:write scopes for this workflow.

1. Connect the MCP server

   Run this command with your API key to connect Claude Code to ThreadMaster. For Cursor, follow the remote-server configuration on the MCP setup page.

   claude mcp add --transport http threadmaster https://threadmaster.ai/api/public/v1/mcp/ --header "Authorization: Bearer tm_live_YOUR_KEY"

2. Ask for a draft

   Ask the assistant to call generate_thread. Save the returned thread id so subsequent calls use this same draft.

   Draft a 7-post thread on lessons from shipping my first API in my usual style. Use generate_thread, then show me the X preview with preview_x_thread. Keep it as a draft.

3. Review and edit the saved thread

   Use get_thread to read the saved content, update_thread to make edits, and preview_x_thread to inspect the final X split before approving it.

   Read the draft with get_thread. Shorten the opening and remove the sales pitch using update_thread, then show me preview_x_thread again. Wait for my approval.

4. Confirm and schedule on X

   Choose a date, time and timezone at least two minutes ahead so the assistant can schedule the approved thread. After confirmation, it calls publish_to_x with thread_id, scheduled_for and a UUID idempotency_key; save the key and returned job id for retries.

   Propose tomorrow at 9am in my timezone as an ISO-8601 scheduled_for with an offset. Show the final thread and ask me to confirm. Once I approve, call publish_to_x with a new UUID idempotency_key; reuse that key if the call must be retried.

5. Check the publishing result and metrics

   After the scheduled time, use list_posts with platform x to locate the job. Use get_post_metrics with platform x and its post_id later to inspect engagement.

   Use list_posts for platform x to find our scheduled job and show its status and permalink. If it has posted, use get_post_metrics with that job's post_id and tell me what engagement is available.

• Require your assistant to confirm with you before any publishing tool runs.
• scheduled_for must be at least two minutes in the future; include the timezone offset.
• The key's scopes decide what the assistant can read, edit or publish. Keep the key private.

Check the API rate limits and quotas before running your workflow at scale.