Schedule Social Posts from NanoClaw

Quick Setup

Use NanoClaw's /customize skill

NanoClaw ships a /customize skill for adding MCP integrations. In your NanoClaw clone, run claude, then /customize, and paste the prompt below. It will update src/index.ts (the mcpServers object) and the relevant groups/*/CLAUDE.md so the agent knows when to use the new tools.

Add the PostFast MCP server to the @marketing group. Service: PostFast (social media scheduling) Command: npx -y postfast-mcp Transport: stdio Env: POSTFAST_API_KEY (I will set this before restart) Update src/index.ts mcpServers, then append a short usage note to groups/marketing/CLAUDE.md explaining PostFast can schedule posts across 11 social platforms. Reference the docs at https://postfa.st/api-integrations/nanoclaw.

Prefer to do it by hand? Three steps:

1. Step 1. Get your PostFast API key. Log in to your PostFast dashboard, open the API section in the sidebar, and generate a key.
2. Step 2. Register PostFast in src/index.ts. NanoClaw configures MCP servers in the mcpServers object passed to the agent. Either use /customize (recommended) or add this block manually:

   {
     "mcpServers": {
       "postfast": {
         "type": "stdio",
         "command": "npx",
         "args": ["-y", "postfast-mcp"],
         "env": {
           "POSTFAST_API_KEY": "your-api-key-here"
         }
       }
     }
   }

   Export the key in your shell profile so it never lands in committed files:

   export POSTFAST_API_KEY="your-api-key-here"

   Append a short usage note to groups/marketing/CLAUDE.md (or whichever group) so the agent knows what PostFast can do.

3. Step 3. Rebuild and message your agent. Rebuild TypeScript and restart the NanoClaw service so the new MCP server is picked up. From WhatsApp, Telegram, or whichever channel that group uses, ping the agent and ask it to schedule a post. The Docker Sandbox spawns, Claude Code calls PostFast, and the agent replies in chat with the scheduled time.

Because every NanoClaw group runs in its own Docker Sandbox, the API key only lives where you put it. If you manage multiple clients, each one gets their own container, their own PostFast key, their own isolated history.