LinkedIn posts with MCP Server and Bolta
One address for any MCP client: https://mcp.bolta.ai/mcp. Parts of the MCP Server 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
The same address works in every app. Where you paste it depends on the app.
For Harbor Coffee, write one LinkedIn post about our new autumn menu and save it for my review.
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 MCP Server
- Confirmed: the address https://mcp.bolta.ai/mcp answers over HTTP and asks for a Bearer token, pointing to OAuth sign-in details. Bolta's own docs describe the browser sign-in and the Bearer API key route.
- Confirmed from the MCP specification: remote servers can ask for OAuth sign-in or accept a bearer token over HTTP.
- Not confirmed: nobody has run a full draft, review and schedule in each MCP client. Bolta's skills repository lists every client except the Claude Code plugin as not tested, and the Claude Code row runs its behavioural checks against a mock Bolta.
- Not confirmed: whether your app's settings screen has a box for an Authorization header. The protocol allows it, but apps differ.
- Menu names and config file locations change between app versions. Use your app's own MCP docs for where to click, and keep the address the same.
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 MCP Server: 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. |
MCP Server jobs for LinkedIn, and how to write them
- Draft a week of posts in your brand voice from inside your app's chat
- Keep one connection per organization and choose brands at sign-in
- 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 MCP Server. Each one asks for a draft and shows you the text first.
For Harbor Coffee, write one LinkedIn post about our new autumn menu and save it for my review.
Save a draft post about our newest feature in my brand voice
Draft a LinkedIn post about what we learned from our last client project and show me the text before saving it
List my LinkedIn accounts in Bolta, then draft one post for the company page and a different one for my own profile
Bolta saves a draft, you read the exact text, you say yes
- 01
Bolta saves a draft
MCP Server 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 MCP Server for LinkedIn
Parts of this route are not confirmed. The note above says which.
For LinkedIn, MCP Server, from Open protocol (Anthropic started it), reaches Bolta through Remote server address, Streamable HTTP. Sign-in: Sign in (OAuth), or a Bearer API key. The LinkedIn account itself is connected inside Bolta, not in MCP Server.
The Bolta MCP server address works in any app that adds remote MCP servers. This page is for apps without a page of their own, and a LinkedIn draft works the same way once your app is connected.
An illustration from the MCP Server guide, not real output. You ask: For Harbor Coffee, write one LinkedIn post about our new autumn menu and save it for my review. The reply goes along these lines: I saved a LinkedIn draft in your brand voice. It is not scheduled and it will not post until you approve it. Want to change the wording first? Draft saved. Waits for your yes.
An illustration from the MCP Server guide, not real output. You ask: Plan a weekly Friday post for Harbor Coffee and show me the plan first. The reply goes along these lines: Proposed plan: a draft each Friday at 9:00, brand time, sent to review before anything goes out. Bolta would run it, so it repeats with this app closed. If you agree I save it switched off, and turning it on is a separate yes from you. Plan shown. Waits for your yes.
To add a brand later, remove Bolta in your app, add it again and tick the new one.
Once connected, your app lists Bolta's tools by name. The kinds are brands and accounts, drafts, the review list, voice and brand details, plans and routines, campaigns, results and replies. Which tools an app is offered can differ by client, so compare your app's list with the full one in the MCP docs.
Your role and the key's permissions decide what each call may do. Anything that changes what goes out, such as approving, scheduling or publishing, needs your yes to that task, and Safe Mode applies on top.
- Review and approval. See what is waiting and send a draft to the team review list. Approval is tied to the exact text, so a changed post needs a fresh yes. Bolta's skills README says batch approval and rejecting with a reason reach Claude and Cursor today, and other apps fall back to one approval at a time or a link to Bolta.
- Campaigns. Attach a web page or file as a source for a campaign of posts. A campaign needs its own go-ahead before it runs. The skills README says campaign set-up from chat reaches Claude and Cursor today, so in another app you may be sent to Bolta for this step.
- The app finds the server. You give your app the address https://mcp.bolta.ai/mcp. The app opens a client for that one server and asks which tools it offers.
- Your brands are listed. list-workspaces returns the brands this connection can reach, and only the ones you ticked at sign-in appear. list-accounts then shows the social accounts connected to a brand, and a draft needs one as its destination.
- Setup: Add a remote server with Bolta's address. Use https://mcp.bolta.ai/mcp and, if asked, the type HTTP (Streamable HTTP). In a JSON file, use the key your app expects: servers or mcpServers for the group, and url, serverUrl or httpUrl for the address. Bolta's server is remote, so choose a remote or HTTP server, not a local command.
- Setup: Save and start the server. Save the setting or file, then start the server if your app leaves that to you. An app that supports sign-in for remote servers should open a Bolta window in your browser.
- REST API. For code you write yourself, with API keys. It does not need an AI app at all. See the API docs.
- Bolta's MCP docs say a routine's drafts wait for review, so what it writes does not go straight out.
- Add the address. In your app's MCP or connectors area, add a remote server named Bolta with the address https://mcp.bolta.ai/mcp. Choose HTTP (Streamable HTTP) if it asks for a type.
Connect MCP Server to Bolta
The same address works in every app. Where you paste it depends on the app.
LinkedIn questions, answered for MCP Server
- How long can a LinkedIn post be when it comes from MCP Server?
- 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 MCP Server should write inside the limit and show you the final text before you say yes.
- Can MCP Server 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.
- What is an MCP server, and do I need one to use Bolta with an AI app?
- An MCP server is how an AI app calls another service in a standard way. You do not run one yourself. Bolta hosts it, and you only add its address to your AI app.
- My app only supports local (stdio) MCP servers. Can I still use Bolta?
- Not directly, since Bolta's server is remote. Update the app and look for a Remote, HTTP or URL option. If there is none, the REST API or an automation tool such as Zapier, Make or n8n is the other way in.
- How long does a sign-in last?
- About 60 days per Bolta's guides, and they usually renew without you doing anything. If a call says Invalid or expired, disconnect Bolta in your app and sign in again.
- The config file is ignored, or the server never starts.
- Check that the JSON is valid with no trailing commas and that the type is http. The top key is servers in VS Code and mcpServers in many other apps. Check your app's MCP log for the real error.
- Does MCP Server publish LinkedIn posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that LinkedIn post. Whether MCP Server completes the connection is not fully confirmed, so read the note above first.
More from MCP Server
MCP Server 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 MCP Server
Connect MCP Server, ask for a LinkedIn draft and read the exact text. Nothing goes live until you say yes.