Post to X from Cursor

Attach PostWharf to Cursor once, then publish or schedule X posts, threads and video by asking for them — and get a receipt saying what actually landed.

Connect it

Declared once in mcpServers, then available from the editor while you work. One workspace key scopes every call to a single brand, so Cursor can only ever reach the accounts in that workspace — not every account you run.

{
  "mcpServers": {
    "wharf": {
      "url": "https://mcp.postwharf.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_WORKSPACE_KEY" }
    }
  }
}

Ask for an X post

Once the server is attached the ask is a prompt in the editor, not a form — in the editor, with the changelog or the release notes already open in front of you:

"Turn these release notes into a four-post thread and queue it for 9am tomorrow."

Cursor finds your connected X channel, checks the text against the 280-character ceiling before anything is queued, and hands back the queued time. Nothing publishes because a model decided it should.

The useful pattern here is turning a diff into an announcement — the file that changed is the context, so the post does not have to be written from memory afterwards.

What X accepts

Character limit280
Counted onone post in a thread
Formatsposts, threads and video

X bills per post at the API level, and link posts cost more than plain text.

What comes back

Every post carries a delivery receipt per channel: the state, the live URL once it is out, and the platform's own reason if it failed. Deliveries are re-checked after publishing, so an X post removed later stops reporting as live instead of sitting in your history as a success. Ask Cursor for the status and it reads that receipt back rather than guessing.

Questions

Can Cursor post to X automatically?

Yes. Connect the PostWharf MCP server to Cursor and it can publish or schedule to a connected X channel, then read the delivery receipt back. The workspace key limits it to the accounts in one workspace, and you keep the approval step.

What do I need before X will work?

X bills per post at the API level, and link posts cost more than plain text. Once the channel is connected in PostWharf, Cursor reaches it the same way it reaches every other network.

How long can a X post be?

280 characters, counted on one post in a thread. PostWharf checks that before the post is queued, so an over-length post is refused immediately rather than failing at X after everything else in the same batch has already published.