---
title: "NanoClaw integration with Bolta"
description: "Connect NanoClaw to Bolta with one ncl command, then draft social posts from WhatsApp, Telegram, Slack or Discord. See what is confirmed, what is not, and where the API key goes."
canonical_url: "https://bolta.ai/integrations/nanoclaw"
markdown_url: "https://bolta.ai/integrations/nanoclaw.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# NanoClaw integration with Bolta

Source: https://bolta.ai/integrations/nanoclaw
Last updated: 2026-11-21

Connect NanoClaw to Bolta with one ncl command, then draft social posts from WhatsApp, Telegram, Slack or Discord. See what is confirmed, what is not, and where the API key goes.

## Summary

Draft social posts from a chat app, with each brand in its own container

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- 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
- Have a scheduled chat job ask for next week's drafts every Friday, with approval still in Bolta
- Ask in Slack or Discord what is waiting for approval, then open the list in Bolta
- Run the agent on your own hardware, with the Bolta key held in the vault instead of in the agent
- Ask for last month's post results in chat before you plan the next batch

## Limitations and boundaries

- 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.
- Integration availability depends on current APIs, authentication, scopes, and account permissions.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## 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.

## Pair a chat app

Use NanoClaw's /add-\<channel\> setup for WhatsApp, Telegram, Slack or Discord so you can message your agent. Do this before adding Bolta, so you can test the result from your phone.

## Connect your social accounts in Bolta

Open Bolta and connect the networks you post to. Without them the agent has nothing to post to, and it will tell you so instead of guessing.

## Create a Bolta API key

In Bolta, open Settings, then API Keys, and create a key that starts with bolta\_sk\_. Pick the brand it is for and give it only the permissions you need.

## 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.

## Add Bolta to your agent group

From the host shell, find your group id and run ncl groups config add-mcp-server --id \<group-id\> --name bolta --url https://mcp.bolta.ai/mcp. Run it on the host, not from inside an agent container, where write commands are approval-gated.

## Restart the group

Changes apply on the next container spawn. Run ncl groups restart --id \<group-id\> so the new server loads now.

## Check what it can see

Message your agent: list my Bolta workspaces and accounts. Confirm it shows the right brands and only the ones you want it to use.

## 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.

## What NanoClaw is

NanoClaw is an open-source, MIT-licensed assistant you host yourself. You message it from a chat app and it runs your request. Each agent group runs in its own isolated containers. For social media, that means you can say draft this week's posts from your phone and have the drafts appear in Bolta's review list. It is built for people who are comfortable with a terminal, since setup uses Docker and the ncl command line.

## Keep the Bolta key in the vault

NanoClaw separates settings the agent can read from secrets it cannot. Where: Credential vault (OneCLI Agent Vault); Safe for the key: Yes; Why: The gateway injects the credential in flight, so the agent never holds it. | Where: --headers; Safe for the key: No; Why: Meant for non-secret header values. | Where: --env; Safe for the key: No; Why: NanoClaw's docs say not to put a raw key here. | Where: The URL; Safe for the key: No; Why: NanoClaw rejects URLs with credentials in them.

## Chat apps and scheduled jobs

Because NanoClaw stays running on your machine, you can message it any time from a paired chat app such as WhatsApp, Telegram, Slack or Discord. You can also ask it to run a job on a schedule, for example a Friday request for next week's drafts. 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.

## One agent group per brand

Add Bolta to each group with its own ncl groups config add-mcp-server command. Because each group runs in its own containers with its own memory, a client's chat history stays in that client's group. When you create a Bolta key, pick the one brand it is for (or tick only that brand) and give it only the permissions it needs. Add that key to that brand's group only.

## Install NanoClaw before you add anything

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.

## Run ncl on the host, not inside the agent

The add-mcp-server command belongs on the machine where NanoClaw is installed. NanoClaw gates ncl write commands that come from inside an agent container, so running it from a chat message will be blocked. Changes apply on the next container spawn. Running ncl groups restart --id \<group-id\> loads the new server straight away.

## Drafting from WhatsApp, Telegram, Slack or Discord

Write the request the way you would to an assistant, and name the brand. The agent saves a draft in Bolta and quotes the text back, so you can read it where you asked. A yes in chat covers the one post you were shown. A different post, or a repeating routine, needs its own yes.

## What is NanoClaw and is it free?

NanoClaw is an open-source, MIT-licensed assistant you install and host yourself. The software is free, though you pay for the hardware you run it on and for any model it uses. Bolta has its own plans and drafts are free.

## 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.

## 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.

## Where does my Bolta key go so the agent cannot read it?

In NanoClaw's credential vault (OneCLI Agent Vault by default), which injects it in flight. Never put it in --env or --headers: NanoClaw says --headers is for non-secret values and not to put a raw key in --env. The exact vault command is not confirmed here.

## Can NanoClaw post to social media without my approval?

No. Bolta keeps drafts in review and refuses unapproved publishing. Safe Mode, roles and any client sign-off still apply, even when a request comes from a chat app.

## 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.

## Which chat apps can I use to talk to NanoClaw?

NanoClaw's docs list WhatsApp, Telegram, Slack, Discord and Signal among others. You pair each one with an /add-\<channel\> setup. Check NanoClaw's docs for the current list.

## 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.

## How do I restart the agent after adding the server?

Run ncl groups restart --id \<group-id\> on the host. Otherwise the change applies the next time the container spawns.

## Is this a verified setup?

Partly. The ncl command, restart and HTTPS rule come from NanoClaw's official docs. The vault step for a Bolta key and OAuth support have not been run end to end, which is why this page shows a caveat.

## 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.

## 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 agent says it has no Bolta tools

Changes apply on the next container spawn. Run ncl groups restart --id \<group-id\> and message the agent again. Also check you added the server to the same group you are chatting with.

## 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.

## 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.

## The add-mcp-server command is blocked

NanoClaw gates ncl write commands that run from inside an agent container. Run the command from the host shell on the machine where NanoClaw is installed.

## It drafts for the wrong brand

Ask it to list your workspaces first and name the brand in the request. For clients, use one agent group per brand so the wrong one cannot be picked.

## The agent says it cannot publish

That is by design. Bolta refuses or sends to review anything you have not approved, and Safe Mode and role limits apply. Approve in Bolta or say yes after it shows the exact text.

## NanoClaw is not OpenClaw

NanoClaw is its own open-source agent, with isolated containers per agent group. OpenClaw is a different self-hosted agent with its own setup, so the steps on this page do not apply to it.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/openclaw](https://bolta.ai/integrations/openclaw)
- [Related page: /integrations/mcp](https://bolta.ai/integrations/mcp)
- [Related page: /integrations/hermes-agent](https://bolta.ai/integrations/hermes-agent)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [NanoClaw official website](https://nanoclaw.dev/)
