Threads 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 Threads until you say yes.
Partly confirmed, see what is and is notChecked 2026-11-21
One JSON entry, then a browser sign-in. No key is needed unless you prefer one.
Draft a Threads post that explains this code pattern to non-developers
Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.
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.
What Bolta does on Threads
Threads caps a post at 500 characters, and Bolta handles longer text by splitting it into a thread of connected posts, so one long idea does not fail.
- Text posts, and posts with images.
- A carousel of 2 to 10 items.
Threads 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 Threads from Cursor: Polls on Threads. Not confirmed for Bolta. Mirroring a Threads post onto Instagram. Threads does not do that on its own, and this page does not confirm that Bolta does it.
| What to know | Threads's own rule | What Bolta does |
|---|---|---|
| Post length | A single Threads post is capped at 500 characters, and a reply carries the same limit. | Bolta uses 500. Longer text is split into a thread of connected posts. |
| Media | A post can carry up to 20 photos or videos in one carousel. Video is limited to 5 minutes and 1 GB. | A carousel in Bolta takes 2 to 10 items. An image over 8 MB is shrunk if Bolta can. |
| Links | Links are allowed, show as a preview card, and are capped at 5 per post. | Each Threads link is swapped at publish time for a short Bolta link that counts clicks. If the swap fails, the link goes out as written. |
| Continuing past the limit | You can continue by replying to your own post, which keeps the follow-on in the same chain. | Send a long text as several parts and Bolta posts every part after the first as a reply, which keeps them in one chain. |
| Formatting | Not stated on this page. | Plain text only on Threads. Markdown is flattened, and tags and mentions stay as typed. |
Cursor jobs for Threads, and how to write them
- Read the README of the project you have open and draft an announcement for a new open-source repo
- Write one longer text when you want a thread, and read where it splits before you say yes.
Example prompts for Threads
Things to type in Cursor. Each one asks for a draft and shows you the text first.
Draft a Threads post that explains this code pattern to non-developers
Which brands and accounts can you reach here?
Read the top entry in CHANGELOG.md and draft a Threads post about it under 500 characters
Look at the latest commits and draft a Threads post about the most visible change
Bolta saves a draft, you read the exact text, you say yes
- 01
Bolta saves a draft
Cursor asks Bolta for the Threads post in your brand voice (save-post). A saved draft is never public.
- 02
You read the exact text
On Threads the exact text includes where a long text is split into a thread and the topic tag, so read each part in order.
- 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.
Using Cursor for Threads
Parts of this route are not confirmed. The note above says which.
For Threads, Cursor, from Anysphere, reaches Bolta through Hosted MCP server in mcp.json. Sign-in: Browser sign-in (OAuth), or an API key header. The Threads account itself is connected inside Bolta, not in Cursor.
Cursor is a code editor, so a Threads 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.
The bolta-skills repo carries a Cursor plugin manifest, but Cursor's docs ask for a marketplace file for the GitHub import and none was seen. Do not count on a team marketplace listing.
The key does not change the approval rule. Bolta still holds anything that has not had your yes.
In Bolta, create a key under Settings, API Keys. It starts with bolta_sk_ and carries only the permissions you tick.
- Review what is waiting. Ask what needs a decision. The agent reads the inbox and approves only the posts you name, after showing the exact text.
- Check how posts did. Ask for last week's results and what to post next without opening a dashboard, so the next release post can borrow what worked.
- It saves a draft. The text the agent wrote from your CHANGELOG.md or diff is stored in Bolta as a draft. It is not scheduled and not live.
- Setup: Sign in and tick your brands. Click sign in next to bolta. Your browser opens on Bolta. Sign in, tick the brands this connection may reach, then go back to Cursor. One connection is one organization. The server should show as connected with a list of tools.
- Setup: Install the Bolta skill. In a terminal run npx skills add boltaai/bolta-skills --skill bolta, and pick Cursor if it asks where to install. Restart Cursor so it finds the skill. This is a route Bolta documents, not a Cursor-official command.
- Cursor plugin or team marketplace. The skills repo has a Cursor plugin manifest, but Cursor's GitHub import asks for a marketplace file that was not seen there.
- A routine you switched on in Bolta keeps running on its own schedule, with no Cursor window needed.
- API key in a header. Choose this if sign-in fails or a script needs it. Add Authorization: Bearer ${env:BOLTA_API_KEY} under headers and keep the key in an environment variable. The key carries only the permissions you tick when you create it. Bolta still waits for your yes before anything is approved or published. Never commit the key.
Connect Cursor to Bolta
One JSON entry, then a browser sign-in. No key is needed unless you prefer one.
Threads questions, answered for Cursor
- What does Bolta do when Cursor writes more than 500 characters for Threads?
- Bolta splits longer text into a thread of connected posts, and the 500 limit also applies to each image caption. The parts are posted as replies in order, so read where the splits fall before you say yes.
- Can Cursor reply to someone else's Threads post?
- Yes, from a public link (reply-to-social-content). The agent writes the text first with the voice-aware draft tool (draft-engagement-reply) (for a stored opportunity) or (draft-inbound-reply) (for a comment on your own post), shows it to you, and calls reply-to-social-content only after your yes, because that call posts the reply. Finding conversations to join (search-engagement-opportunities) needs a campaign already attached to the account.
- Can I post to social media from Cursor?
- Cursor's agent can ask Bolta to draft, save and, after you say yes, schedule posts to the accounts you connected in Bolta. It does not post from your machine. This route follows Cursor's docs but has not been tested end to end by Bolta.
- How do I install the Bolta skill in Cursor?
- Run npx skills add boltaai/bolta-skills --skill bolta, pick Cursor if asked, and restart Cursor. This is a Bolta route using the skills CLI, not a Cursor command. Cursor loads skills from .cursor/skills and .agents/skills.
- 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.
- Cursor connects but sees no brand, or the wrong one
- The brand was not ticked at sign-in. Disconnect bolta, connect again and tick every brand you want. A brand you add later needs a reconnect. When you have several brands, name the one you mean in your request.
- Does Cursor publish Threads posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that Threads 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.
Threads from other AI agents
The same Threads limits apply whichever agent asks. The connection and the setup are what change.
Try a Threads draft from Cursor
Connect Cursor, ask for a Threads draft and read the exact text. Nothing goes live until you say yes.