Bluesky 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 Bluesky 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.
Do I have a Bluesky account connected for this brand?
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 Bluesky
Bolta cuts Bluesky text at 300 characters and ends it with an ellipsis, so the useful part of a draft has to come before the limit.
- Text posts of up to 300 characters, cut with an ellipsis beyond that.
- Images. A video is left off, and Bolta publishes the text and any images.
Bluesky limits and format rules
Bolta's posting rules for your workspace (get-posting-rules) win if they differ from this page.
Not promised for Bluesky from NanoClaw: Custom feeds and quote posts. Neither is confirmed for Bolta. Any Bluesky rule beyond what Bolta reports. This page states Bolta's limits, not a network rulebook.
| What to know | Bluesky's own rule | What Bolta does |
|---|---|---|
| Post length | Not stated on this page. | 300 characters. Longer text is cut short and ends with an ellipsis. |
| Media | Not stated on this page. | Images are posted. A video is skipped with a warning, and the text and any images still go out. |
| Threads | Not stated on this page. | Parts after the first are posted as replies, so they read as one Bluesky thread. |
| Formatting | Not stated on this page. | Bluesky shows plain text, so Bolta flattens markdown and leaves #hashtags and @mentions as typed. |
NanoClaw jobs for Bluesky, and how to write them
- Have a scheduled chat job ask for next week's drafts every Friday, with approval still in Bolta
- Write to 300 characters yourself. The cut is blunt and ends in an ellipsis.
Example prompts for Bluesky
Things to type in NanoClaw. Each one asks for a draft and shows you the text first.
Do I have a Bluesky account connected for this brand?
Show me last month's results for the Acme brand before I plan the next batch.
Draft a Bluesky post under 300 characters about our new guide and show me the text before saving
Draft a Bluesky post to go with two images from my library and show me the text before saving
Bolta saves a draft, you read the exact text, you say yes
- 01
Bolta saves a draft
NanoClaw asks Bolta for the Bluesky post in your brand voice (save-post). A saved draft is never public.
- 02
You read the exact text
On Bluesky the exact text includes where the 300-character cut would fall, and which images are attached, because a video would be left off.
- 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 Bluesky
Parts of this route are not confirmed. The note above says which.
For Bluesky, 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 Bluesky 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 Bluesky 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 Bluesky post it saves, so keep them on.
An illustration from the NanoClaw guide, not real output. You ask: Do I have a Bluesky account connected for this brand? The reply goes along these lines: Here is what is connected to that workspace. If Bluesky is missing, I can ask Bolta for a connect link that you open yourself. Read only. Nothing changed.
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.
NanoClaw is cloned from github.com/nanocoai/nanoclaw and set up with bash nanoclaw.sh. It needs Docker, pnpm and Node.js, and the README holds the current versions.
Pair one chat app first and confirm you can message the agent. Adding Bolta to a group that you cannot reach from your phone makes it hard to tell which part failed.
- Review queue from chat. Ask what is waiting and the agent reads your inbox. Sending drafts to review or approving them happens only after you say yes for that task.
- Weekly drafting as a routine. A repeating job is planned first, saved switched off, and only turned on after a separate yes from you.
- It checks which brand you mean. The agent lists your workspaces so a draft for one brand is not written under another. If you have several, it asks before going further.
- You decide in chat or in Bolta. The agent shows the exact text in the chat. Sending it to review, approving, scheduling or publishing happens only after you say yes for that post.
- Setup: Install NanoClaw if you have not. Clone github.com/nanocoai/nanoclaw and run bash nanoclaw.sh. You need Docker, pnpm 10 or newer and a current Node.js, so check the README for exact versions. Each agent group runs in its own containers.
- Setup: Restart the group. Changes apply on the next container spawn. Run ncl groups restart --id <group-id> so the new server loads now.
- Bolta REST API. Bolta has a public API, but nobody has wired it into a NanoClaw group and checked it. The MCP route is the one this page follows.
- A Bolta routine runs on Bolta's side once you have confirmed it, even if NanoClaw is stopped. It stays switched off until you say yes to turning it on.
- Ask in your chat app. Message the agent: list my Bolta workspaces and accounts. Then ask for drafts. They land in review and wait for your yes.
Connect NanoClaw to Bolta
NanoClaw runs on your own hardware, so you add the server address https://mcp.bolta.ai/mcp on that machine.
Bluesky questions, answered for NanoClaw
- Can NanoClaw post a video to Bluesky?
- Not through Bolta. Bolta publishes the text and any images and leaves a video off, with a warning. Use images, or post the video on another network.
- What is the Bluesky length limit for posts from NanoClaw?
- 300 characters. Longer text is cut short and ends with an ellipsis, so write to the limit and read the final text before you say yes.
- How do I add Bolta to NanoClaw?
- On the host machine, run ncl groups config add-mcp-server --id <group-id> --name bolta --url https://mcp.bolta.ai/mcp, then ncl groups restart --id <group-id>. Add your Bolta key through NanoClaw's credential vault, not in that command.
- Can I use a different NanoClaw agent group for each brand?
- Yes, and it is a good fit for agencies. Add Bolta to each group separately, so each brand gets its own containers. Create one Bolta key per brand and add it to that brand's group only.
- Does NanoClaw need to stay on for Bolta drafts to exist?
- Only to create new ones through chat. Drafts already saved in Bolta stay there if the host is switched off. A Bolta routine you confirmed keeps running on Bolta's side.
- ncl rejects the URL
- NanoClaw needs an HTTPS URL with no credentials in it. Use exactly https://mcp.bolta.ai/mcp with no key or token in the address.
- Does NanoClaw publish Bluesky posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that Bluesky 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.
Bluesky from other AI agents
The same Bluesky limits apply whichever agent asks. The connection and the setup are what change.
Try a Bluesky draft from NanoClaw
Connect NanoClaw, ask for a Bluesky draft and read the exact text. Nothing goes live until you say yes.