# Schedule Social Media Posts with nanoclaw

nanoclaw (open-source agent by NanoCo)

Guide: https://lots.social/agents/nanoclaw

nanoclaw runs agents in containers. LotsSocial provides a remote publishing interface, so social-account access and scheduled delivery can stay with the hosted service.

Example workflow: Prepare a LinkedIn draft from these release notes using the LotsSocial connection configured for this runtime. Do not schedule it yet.

**Configure the actual container runtime.** The connection must exist where the nanoclaw agent executes. An MCP entry on your laptop does not automatically configure the running container.

**Use a supported tool connection.** Add the remote HTTP MCP entry to your group’s container configuration. Give its credential gateway a LotsSocial API key and allow the group to use that connection.

**Let the hosted queue hold the time.** Once a post has an approved schedule in LotsSocial, its delivery does not depend on keeping that container conversation open.

### How do I connect nanoclaw to LotsSocial?

Follow the nanoclaw setup below to add https://api.lots.social/mcp. Configure your LotsSocial API key using the credential settings shown. Ask your agent to list your connected accounts, then save your first post as a draft.

### Is nanoclaw the same installation as OpenClaw?

No. They are separate projects and runtimes. Follow nanoclaw’s group configuration and credential-gateway steps below; OpenClaw has its own MCP setup.

### Which social platforms can nanoclaw schedule posts to through LotsSocial?

Once a compatible connection has write access, LotsSocial provides publishing and scheduling for 12 networks: LinkedIn, Instagram, X, Google Business, Facebook, YouTube, Reddit, Threads, TikTok, Pinterest, Bluesky, Mastodon. Connect your accounts first. Formats, media requirements and available analytics vary by platform.

### Can nanoclaw save social posts as drafts before scheduling?

Yes, through a compatible connection with write tools. Ask for drafts explicitly and review the captions, media and accounts. Drafts remain unscheduled until you ask to schedule them; you choose when to schedule them.

### Will scheduled posts publish after I close nanoclaw?

Once a post is successfully scheduled in LotsSocial, its publishing queue handles delivery at the chosen time even when your agent is closed. Creating new drafts or running a recurring brief still requires your agent. Check post status for platform rejections or failed deliveries.

### Do I need a subscription to use LotsSocial with nanoclaw?

No LotsSocial subscription is required. Pick a plan for a fixed monthly price, or pay per connected account with credits, charged daily. Eligible new users receive free starter credits with no card required, valid for 90 days. Media storage is free and purchased credits never expire. Your agent’s own plan or usage fees are separate. Current rates are on the LotsSocial pricing page.

### Can nanoclaw manage multiple brands with LotsSocial?

Through a compatible connection, your agent can work with brands and their connected accounts inside a workspace. Separate businesses can have separate workspaces. Brands, workspaces, posts and team members are unlimited; connected accounts are covered by your plan or funded with credits.

### The server is configured but requests are blocked

Check your credential gateway’s connection, group grant and network policy for api.lots.social. The remote MCP entry alone does not authorize network access or supply credentials.

Needs:
- A current nanoclaw installation with remote HTTP MCP support
- Administrator access to its group configuration and credential gateway
- A LotsSocial API key

Steps:
1. **Add the server to your agent’s group.** On the host, merge this entry into mcpServers in groups/<group-folder>/container.json. Keep the group’s existing configuration. nanoclaw mounts this file into the agent container at startup.
   `{
  "mcpServers": {
    "lotssocial": {
      "type": "http",
      "url": "https://api.lots.social/mcp"
    }
  }
}`
2. **Configure the credential gateway.** Create a LotsSocial API key in the Lots API dashboard. Store it in your installation’s credential gateway, scoped to api.lots.social, and configure the Authorization header as Bearer followed by the key. Allow the social agent’s group to use that connection; keep the real key out of container.json.
3. **Start a new agent session.** Restart the affected agent session so it loads the server. Ask nanoclaw to list your connected accounts, then save a draft. Review it before asking for a publication time.

Official setup documentation: [nanoclaw: runner configuration](https://github.com/nanocoai/nanoclaw/blob/main/container/agent-runner/src/config.ts), [nanoclaw: credential gateways](https://github.com/nanocoai/nanoclaw/blob/main/docs/gateway-seam.md)