Cursor + X (Twitter)

X (Twitter) posts with Cursor and Bolta

Turn what you just shipped into social posts, from inside the editor. Parts of the Cursor route are not confirmed yet, and the note below says which. Nothing goes live on X until you say yes.

One JSON entry, then a browser sign-in. No key is needed unless you prefer one.

CursorBolta connected
You

Write an X post about the API feature I just shipped and save it as a draft

Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.

Illustration. Your drafts show your real text, account and time.

What is and is not confirmed

Read this before you set up Cursor

  • Confirmed from Cursor's own docs: remote MCP servers go in mcp.json with a url, Cursor supports OAuth sign-in for them, and skills load from .cursor/skills and ~/.cursor/skills. Bolta's server is a remote MCP server of exactly that kind.
  • Not confirmed: nobody at Bolta has run a full draft, review and schedule round trip inside Cursor. The config and the skill follow Cursor's docs, but the sign-in handshake with mcp.bolta.ai has not been watched end to end.
  • Not confirmed: whether the Bolta skill can be imported into a Cursor team marketplace as it stands. Do not expect a one-click import from GitHub.
  • Cursor's menu labels change between versions. Where this page names a menu, look for the MCP servers list if the label differs.
  • Bolta takes media as a public link, not as an upload from Cursor. Instagram and Pinterest posts need an image or video, and TikTok and YouTube need a video.
Bolta on X

What Bolta does on X

Bolta reads the limit for each connected X account, so a Premium account and a free account get different ceilings. Text that is too long does not get trimmed on X: the post fails, so the draft has to fit first.

  • Single posts and threads. In a thread, Bolta posts every part after the first as a reply to the one before.
  • Images. A post needs text: an image with no text is not supported on X.
Limits and format

X limits and format rules

Network rules last checked 2026-07-28. Bolta's posting rules for your workspace (get-posting-rules) win if they differ from this page.

Not promised for X from Cursor: Polls and Spaces announcements. Neither is confirmed for Bolta. How many hashtags work best. Bolta checks none, and this page makes no claim about it.

X limits and format rules
What to knowX's own ruleWhat Bolta does
Post lengthAccounts without a paid subscription are limited to 280 characters. X Premium subscribers can publish up to 25,000.Bolta reads the limit per account. Longer text makes the post fail, so shorten it first. The 25,000 limit is a ceiling for Premium accounts, and X can still refuse a long post.
Links and mediaA pasted link counts as 23 characters however long it is. Photos, videos and GIFs count as zero characters.Bolta does not check how many hashtags you use or their format. They are kept as typed.
ThreadsPosts can be chained into a thread, and each post carries its own separate character limit.Each X thread part after the first is posted as a reply to the one before it.
Who can replyReplies can be limited to everyone, accounts you follow, verified accounts, or only the accounts you mention. It is chosen before you post.The default is that anyone can reply unless you limit it.
VideoNot stated on this page.Video on X is checked on X's side for duration, format and posting eligibility, so a successful upload does not guarantee publication. Ask for the posting rules before you attach one.
Best practices

Cursor jobs for X, and how to write them

  • Draft a devrel week of posts: one release note, one how-it-works, one lesson learned
  • Write to 280 unless the account has X Premium. Check the count, because a post over the limit fails instead of being cut.
Prompts

Example prompts for X

Things to type in Cursor. Each one asks for a draft and shows you the text first.

Write an X post about the API feature I just shipped and save it as a draft

Draft an X post that explains the retry logic in this diff for people who do not code.

Read the top entry in CHANGELOG.md and draft an X post about it that fits in 280 characters

Look at the newest tagged release and draft an X post with a link to it

Review

Bolta saves a draft, you read the exact text, you say yes

  1. 01

    Bolta saves a draft

    Cursor asks Bolta for the X post in your brand voice (save-post). A saved draft is never public.

  2. 02

    You read the exact text

    On X the exact text includes the character count with links counted at 23, and, for a thread, every part in order.

  3. 03

    You say yes

    Only then does Bolta schedule or publish (publish-post), in your workspace's timezone. Safe Mode, client sign-off and brand approval rules still apply.

Cursor and Bolta

Using Cursor for X

Parts of this route are not confirmed. The note above says which.

For X, Cursor, from Anysphere, reaches Bolta through Hosted MCP server in mcp.json. Sign-in: Browser sign-in (OAuth), or an API key header. The X account itself is connected inside Bolta, not in Cursor.

Cursor is a code editor, so an X draft can start from a changelog, a commit or the README in the open project. The draft is stored in Bolta, so a scheduled post does not need Cursor to stay open.

An illustration from the Cursor guide, not real output. You ask: Draft an X post that explains the retry logic in this diff for people who do not code. The reply goes along these lines: I read the selected diff and wrote a short post about what customers notice: failed imports now try again on their own. I checked the X rules first. It is saved as a draft. I have not scheduled or published it. Draft saved. Waits for your yes.

How it works: a short thread on X that explains one design choice from a file you have open.

Bolta stores the result. The agent does not post from your machine, so the draft is waiting in Bolta for review whether or not Cursor stays open.

You can also run several agent tabs. One can draft a week of posts while another works on code. Each draft still waits in Bolta for your yes.

  • Send a draft to a human reviewer. If a teammate or client signs off first, the agent can hand a saved draft to review instead of approving it itself.
  • Plan a recurring release post. Describe a Monday release note in plain words. The agent shows a plan, saves it switched off, and turning it on is a separate yes.
  • It reads your voice. Bolta returns the brand voice and facts it holds, so a post about your release sounds like you and not like a generic changelog summary.
  • Setup: Optional: use an API key instead of sign-in. Create a Bolta API key in Bolta under Settings, API Keys (it starts with bolta_sk_, and carries only the permissions you tick), store it in an environment variable, and add "headers":{"Authorization":"Bearer ${env:BOLTA_API_KEY}"} to the bolta entry. Keep the key out of git.
  • Setup: Check what is waiting. Ask: Which drafts in Bolta are waiting for me? Nothing is approved, scheduled or published until you say yes to the exact text.
  • Skill via npx skills add. npx skills add boltaai/bolta-skills --skill bolta, choosing Cursor. It is a Bolta route, not a Cursor command, and where it writes (.cursor/skills or .agents/skills) is not confirmed.
  • Drafts and the approval inbox stay in Bolta. Open them in the web app or in any other connected agent.
  • Browser sign-in (OAuth). Choose this on your own machine. Cursor opens Bolta in the browser, you sign in and tick your brands. No secret sits in a file. Cursor's docs say it uses dynamic client registration for this unless you set static credentials. That handshake against Bolta has not been watched end to end.
Connect

Connect Cursor to Bolta

One JSON entry, then a browser sign-in. No key is needed unless you prefer one.

FAQ

X questions, answered for Cursor

What happens if Cursor writes an X post that is too long?
The post fails. Bolta does not trim X text, so Cursor has to shorten it first. The limit is 280 characters for accounts without a paid subscription, and X Premium accounts can post up to 25,000, though X can still refuse a long post.
Can Cursor write an X thread?
Yes. Ask for several parts, and Bolta posts each part after the first as a reply to the one before it, so they read as one thread. Each part carries its own limit. You read all of the parts in Cursor and say yes before any of them goes out.
Does Bolta work with Cursor's agent in several tabs?
Cursor lets you run several agent tabs, so one can draft posts while another edits code. Bolta has not tested parallel use, so check the inbox if two tabs draft for the same brand.
How is Bolta in Cursor different from Claude Code or Codex?
Cursor is an editor with the project open, so drafts come from files you can see. Claude Code and Codex are terminal agents with their own install commands. The approval rule is the same everywhere, but the set of Bolta tools offered can differ by app.
Can the Cursor agent read my git history to write a post?
Cursor's agent reads what Cursor lets it read in your project, such as files, a selected diff or commit text you paste. Bolta never sees your repository. It receives only the draft text and settings the agent sends in a tool call.
Is my code sent to Bolta?
Only what the agent puts into a Bolta tool call, which is normally the post text and the brand you chose. What Cursor sends to its own model is governed by Cursor's settings. Bolta has not audited that side, so check Cursor's privacy options if the code is sensitive.
Does Cursor publish X posts without my yes?
No. Nothing is approved, scheduled or published until you say yes to that X post. Whether Cursor completes the connection is not fully confirmed, so read the note above first.

More from Cursor

Cursor can work with the other networks Bolta publishes to. Each page has its own limits and review notes.

X from other AI agents

The same X limits apply whichever agent asks. The connection and the setup are what change.

Try an X draft from Cursor

Connect Cursor, ask for an X draft and read the exact text. Nothing goes live until you say yes.