Schedule Social Media Posts with 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.
Eligible new users get free credits, valid for 90 days. No card required.
Example workflow
“Prepare a LinkedIn draft from these release notes using the LotsSocial connection configured for this runtime. Do not schedule it yet.”
Your container agent prepares the content; LotsSocial saves the draft in your calendar.
A container task with a hosted publishing handoff
01
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.
02
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.
03
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.
What can nanoclaw do with LotsSocial?
With a compatible connection, your agent can save drafts, schedule posts with images or video, manage connected accounts and retrieve available analytics. LotsSocial handles the publishing schedule; your agent supplies the content and instructions.
Supported networks: LinkedIn, Instagram, X, Google Business, Facebook, YouTube, Reddit, Threads, TikTok, Pinterest, Bluesky, Mastodon. Platform-specific formats and media requirements still apply.
You need
- A current nanoclaw installation with remote HTTP MCP support
- Administrator access to its group configuration and credential gateway
- A LotsSocial API key
- A LotsSocial account, which is created when you first sign in. No card required.
Connect nanoclaw to LotsSocial
- 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.
What to ask next
- “List my connected social accounts”
- “Draft a launch post for LinkedIn and X; save both as drafts for me to review”
Once connected, when you ask to connect an account, your agent gives you a link to open in your browser. Approve access on the network’s own page; the link works for an hour.
If something goes wrong
- 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.
Official setup documentation: nanoclaw: runner configuration, nanoclaw: credential gateways.
MCP or REST API: use the connection your agent supports.
The remote MCP endpoint is shared. For scripts or an agent with HTTP tools, use the REST API and an API key.
https://api.lots.social/mcp