LinkedIn 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 LinkedIn 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.
We tagged 2.0 today. Write a LinkedIn post from the top entry in CHANGELOG.md
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 LinkedIn
Bolta writes the text, saves it as a draft on the account you name, and waits. Bolta lists each LinkedIn organization as its own account, so a company page is a separate choice from your personal profile.
- Text posts to a personal profile or to a company page you have connected.
- Posts visible to everyone by default, or to connections only if you ask for that.
LinkedIn 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 LinkedIn from Cursor: LinkedIn articles, newsletters and document carousels. LinkedIn supports them, but this page does not confirm that Bolta publishes them. Comment length limits. The one checked limit on this page is the feed post.
| What to know | LinkedIn's own rule | What Bolta does |
|---|---|---|
| Post length | A feed post is capped at 3,000 characters, counting spaces, line breaks, emoji and the full text of any link you paste. | Bolta does not check LinkedIn text length, so LinkedIn may refuse longer text. The draft has to fit before you say yes. |
| Opening lines | The feed cuts a post after the first few lines behind a see more link. | Bolta keeps your first lines as written. Put the point there. |
| Formatting | Not stated on this page. | Plain text only. Bold, italic and headings become look-alike characters, a list becomes bullets, and a link is written as label (url). #hashtags and @mentions are kept as typed. |
| Who can see it | Not stated on this page. | Everyone, unless you set the post to connections only. |
Cursor jobs for LinkedIn, and how to write them
- Turn the newest CHANGELOG.md entry into a LinkedIn launch post while the release is still open in your tabs
- Check how last week's posts did before you plan the next batch, without opening another app
- Write to 3,000 characters including spaces, line breaks, emoji and any pasted link, because Bolta will not stop a post that is too long.
Example prompts for LinkedIn
Things to type in Cursor. Each one asks for a draft and shows you the text first.
We tagged 2.0 today. Write a LinkedIn post from the top entry in CHANGELOG.md
Read CHANGELOG.md and draft a LinkedIn post about the 2.0 release in my voice.
Read the top entry in CHANGELOG.md and save a LinkedIn draft about it for my review
Look at the last five commits and draft a LinkedIn post about what changed, without markdown
Bolta saves a draft, you read the exact text, you say yes
- 01
Bolta saves a draft
Cursor asks Bolta for the LinkedIn post in your brand voice (save-post). A saved draft is never public.
- 02
You read the exact text
On LinkedIn the exact text includes where the line breaks fall, because the feed hides everything after the first few lines, and how any formatting was flattened to plain text.
- 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 LinkedIn
Parts of this route are not confirmed. The note above says which.
For LinkedIn, Cursor, from Anysphere, reaches Bolta through Hosted MCP server in mcp.json. Sign-in: Browser sign-in (OAuth), or an API key header. The LinkedIn account itself is connected inside Bolta, not in Cursor.
Cursor is a code editor, so a LinkedIn 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: Read CHANGELOG.md and draft a LinkedIn post about the 2.0 release in my voice. The reply goes along these lines: I read the 2.0 section and drafted a post that leads with the faster import and mentions the two fixes. It is saved as a draft in Bolta. I have not scheduled it. Want changes, or shall I schedule it? Draft saved. Waits for your yes.
An illustration from the Cursor guide, not real output. You ask: Plan a weekly Monday post about what we shipped. Do not switch it on yet. The reply goes along these lines: Here is the plan: one LinkedIn draft every Monday at 9:00 workspace time, built from the week's release notes, sent to review. Nothing is saved yet. Say yes and I will save it switched off. Turning it on is a separate yes. Plan shown. Nothing saved. Waits for your yes.
Release note: the newest CHANGELOG.md section as one LinkedIn post, with the user-facing change first.
Lesson learned: a post about a bug you just fixed, written for readers who do not know your codebase.
Launch week: three drafts over five days, saved together so you can review them in one pass.
- Add a missing account. If a brand has no LinkedIn yet, the agent can fetch a connect link for you to open. The sign-in itself happens in your browser.
- 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.
- 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.
- The agent finds your brand. It asks Bolta which brands this connection may reach. Only the brands you ticked at sign-in show up, so a brand you skipped never appears here.
- Setup: Say set me up. Open Agent chat and type set me up. Answer the questions about your brand, voice and accounts. Then try: Draft a LinkedIn post about the release in CHANGELOG.md and save it as a draft.
- Setup: Have a Bolta brand with an account connected. Sign in at bolta.ai, set up at least one brand and connect at least one social account. The agent can only draft for brands and accounts that exist there.
- Hosted MCP with an API key header. Add Authorization: Bearer ${env:BOLTA_API_KEY} under headers. Cursor's docs show headers and ${env:NAME} expansion. Not tested against Bolta by Bolta.
- A post you approved and scheduled in Bolta publishes at its time even if you quit Cursor or close the laptop.
- Ask the agent for a post. Say: Draft a LinkedIn post about the release in CHANGELOG.md and save it as a draft. Bolta stores it and waits for your yes.
Connect Cursor to Bolta
One JSON entry, then a browser sign-in. No key is needed unless you prefer one.
LinkedIn questions, answered for Cursor
- How long can a LinkedIn post be when it comes from Cursor?
- A LinkedIn feed post is capped at 3,000 characters, and the count includes spaces, line breaks, emoji and the full text of any link you paste. Bolta does not check LinkedIn length, so Cursor should write inside the limit and show you the final text before you say yes.
- Can Cursor post to a LinkedIn company page and not only my profile?
- Bolta lists each LinkedIn organization as its own account, so you can name the page when you ask (list-accounts). The company page has to be connected in Bolta first. If it is not there, ask for a connect link (get-connect-link) and finish the sign-in in your browser.
- Does Bolta publish without my approval from Cursor?
- No. The agent should show you the exact text first, and Bolta refuses or holds anything that has not been approved. Nothing is approved, scheduled or published until you say yes.
- Which brands can Cursor reach if I have several?
- The ones you ticked when you signed in. One connection is one organization. Name the brand in your request, and reconnect to add a new one.
- 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.
- 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 LinkedIn posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that LinkedIn 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.
LinkedIn from other AI agents
The same LinkedIn limits apply whichever agent asks. The connection and the setup are what change.
Try a LinkedIn draft from Cursor
Connect Cursor, ask for a LinkedIn draft and read the exact text. Nothing goes live until you say yes.