LinkedIn posts with NanoClaw and Bolta
Draft social posts from a chat app, with each brand in its own container. Parts of the NanoClaw 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
NanoClaw runs on your own hardware, so you add the server address https://mcp.bolta.ai/mcp on that machine.
Draft three LinkedIn posts about our launch and send them to 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 NanoClaw
- Confirmed from NanoClaw's official docs: you can add a remote Streamable HTTP MCP server to an agent group with ncl groups config add-mcp-server --id <group-id> --name <name> --url <https url>. The URL must be HTTPS and cannot carry credentials, which https://mcp.bolta.ai/mcp satisfies.
- Confirmed from the docs: --headers is for non-secret values only, and real credentials belong in the credential gateway vault (OneCLI Agent Vault by default), which injects them in flight. The docs also say not to put a raw key in --env.
- Not confirmed: the exact vault command for storing a Bolta key, and a worked example of the vault injecting a Bearer bolta_sk_ key for a custom MCP host. This page does not write out a one-line Authorization header, because none is documented.
- Not confirmed: whether NanoClaw's remote MCP servers support OAuth sign-in, and whether Bolta's skill works inside its agent containers. Neither has been run end to end.
- Whatever works on the NanoClaw side, Bolta does not change: nothing is approved, scheduled or published until you say yes.
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 NanoClaw: 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. |
NanoClaw jobs for LinkedIn, and how to write them
- Send a one-line message from your phone and get a LinkedIn draft back before you leave the train
- Give each client brand its own agent group, so each client stays in its own containers
- 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 NanoClaw. Each one asks for a draft and shows you the text first.
Draft three LinkedIn posts about our launch and send them to review
Draft a LinkedIn post about our spring release.
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
NanoClaw 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 NanoClaw for LinkedIn
Parts of this route are not confirmed. The note above says which.
For LinkedIn, NanoClaw, from NanoClaw (open source, MIT licence), reaches Bolta through Remote MCP server added to an agent group with ncl. Sign-in: API key held in NanoClaw's credential vault (OAuth not confirmed). The LinkedIn account itself is connected inside Bolta, not in NanoClaw.
NanoClaw runs on your own hardware and is messaged from chat apps, so you can say 'draft this week's LinkedIn posts' there. Its docs say real credentials belong in a vault, so the agent itself does not hold the Bolta key.
This connection uses a Bolta API key, which acts as you. Safe Mode and client sign-off still apply to every LinkedIn post it saves, so keep them on.
An illustration from the NanoClaw guide, not real output. You ask: Draft a LinkedIn post about our spring release. The reply goes along these lines: I saved one LinkedIn draft in your brand voice. Nothing is approved, scheduled or published. Want me to show the exact text here before you decide? Draft saved. Waits for your yes.
An illustration from the NanoClaw guide, not real output. You ask: Rewrite the draft you just saved so it opens with the question. The reply goes along these lines: I will change the draft text and leave it waiting. I will not approve, schedule or publish it. Draft updated. Waits for your yes.
A scheduled chat job can only do what the agent can already do. It drafts and sends to review. Publishing still needs your yes, and a repeating Bolta routine needs its own separate confirmation before it is switched on.
Changes apply on the next container spawn. Running ncl groups restart --id <group-id> loads the new server straight away.
A yes in chat covers the one post you were shown. A different post, or a repeating routine, needs its own yes.
- Drafts from a phone message. Ask for a post in one line and the agent saves it to Bolta as a draft in your brand voice, then shows you the text.
- One brand per agent group. Each group runs in its own containers with its own memory, and you can name the workspace in every request so drafts do not cross brands.
- It reads your voice and the posting rules. Before writing, it pulls the saved voice context and the rules for the network, so length and tone match what you have already set up.
- It saves the draft, nothing more. The text is stored in Bolta as a draft. It is not approved, not scheduled and not published.
- Setup: Ask for a draft. Try: draft three LinkedIn posts about our launch and send them to review. Drafts are free. Approve, schedule or publish them in Bolta, or say yes in chat after the agent shows the exact text.
- Setup: Put the key in NanoClaw's vault. Store it in the credential gateway vault (OneCLI Agent Vault by default) so the key is injected when the agent calls Bolta. Do not paste it into --env or --headers: NanoClaw's docs say --headers is for non-secret values and not to put a raw key in --env. The exact vault command is not confirmed here, so follow NanoClaw's own vault docs.
- Remote MCP server added with ncl. NanoClaw's docs describe ncl groups config add-mcp-server with an HTTPS URL, so https://mcp.bolta.ai/mcp can be registered on a group, then restart the group. The sign-in step is not documented for this host, so the full route has not been run end to end.
- A scheduled job such as a Friday drafting request can only draft and send to review.
- Hosted MCP server. Choose this for almost everyone. Point a group at https://mcp.bolta.ai/mcp with ncl groups config add-mcp-server. Bolta keeps its own tools and approval rules, and you update nothing when they change.
Connect NanoClaw to Bolta
NanoClaw runs on your own hardware, so you add the server address https://mcp.bolta.ai/mcp on that machine.
LinkedIn questions, answered for NanoClaw
- How long can a LinkedIn post be when it comes from NanoClaw?
- 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 NanoClaw should write inside the limit and show you the final text before you say yes.
- Can NanoClaw 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.
- Do I need an API key or can I sign in with OAuth?
- Plan on an API key from Settings, API Keys in Bolta. Whether NanoClaw's remote MCP servers support OAuth sign-in is not described in its docs, so this page does not promise it.
- Does NanoClaw work with the Bolta skill?
- Not confirmed. NanoClaw documents skills as SKILL.md workflows, but an npx skills install is not described there, and Bolta's skill has not been tested in its containers. The hosted MCP server is the documented route.
- Can I use NanoClaw without Docker?
- NanoClaw's documented setup uses Docker, and each agent group runs in its own containers. This page does not cover a Docker-free setup because none is described in the docs it relies on.
- The server loads but Bolta calls fail with an authorization error
- The key is probably not reaching Bolta. Check it starts with bolta_sk_, has the permissions you need, and that the vault is set to inject it for this host. This page cannot confirm the vault steps, so use NanoClaw's own vault docs.
- Does NanoClaw publish LinkedIn posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that LinkedIn post. Whether NanoClaw completes the connection is not fully confirmed, so read the note above first.
More from NanoClaw
NanoClaw 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 NanoClaw
Connect NanoClaw, ask for a LinkedIn draft and read the exact text. Nothing goes live until you say yes.