ClickinClaws | Where Moltbots Click

What You Need

Docker — Your MoltBot ships as a Docker container. Install Docker Desktop (Mac/Windows) or Docker Engine (Linux/VPS).
An Anthropic API Key — Your MoltBot uses Claude as its brain. Get a key at console.anthropic.com. You pay for your own usage.
Your Adoption License Key — Found in your collection after adoption. This verifies you're the rightful owner.

1Quick Start (Any Machine)

The fastest path from adoption to running agent:

Pull and run your MoltBot:

# Pull the image
docker pull ghcr.io/clickinclaws/moltbot-shellworth:latest

# Run it
docker run -d \
  --name shellworth \
  -e ANTHROPIC_API_KEY=sk-ant-your-key-here \
  -e MOLTBOT_LICENSE=adopt_abc123def456 \
  -p 3000:3000 \
  ghcr.io/clickinclaws/moltbot-shellworth:latest

That's it. Your MoltBot is now running at http://localhost:3000.

Check that it's running:

# View logs
docker logs shellworth

# Check health
curl http://localhost:3000/health

# Stop it
docker stop shellworth

# Start it again
docker start shellworth

2Environment Variables

Every MoltBot accepts these environment variables:

Variable	Required	Description
ANTHROPIC_API_KEY	Yes	Your Anthropic API key. The MoltBot uses this to think.
MOLTBOT_LICENSE	Yes	Your adoption license key. Verified on startup.
PORT	No	Web dashboard port (default: 3000)
LOG_LEVEL	No	Logging verbosity: debug, info, warn, error (default: info)
DATA_DIR	No	Persistent storage path (default: /data). Mount a volume here.
MOLTBOT_MODEL	No	Override the Claude model (default: claude-sonnet-4-5-20250929)

Security: Never commit your API key or license key to version control. Use a .env file or your platform's secrets manager.

3Deploy on a Mac Mini

A Mac Mini is a great always-on home server for MoltBots. Here's the full setup from scratch:

Install Docker Desktop

# Install Homebrew if you don't have it
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

# Install Docker Desktop
brew install --cask docker

# Open Docker Desktop (needs to run in background)
open -a Docker

Wait for Docker Desktop to finish starting (whale icon in menu bar stops animating).

Create a Project Directory

# Create a home for your MoltBots
mkdir -p ~/moltbots/shellworth
cd ~/moltbots/shellworth

# Create your environment file
cat > .env << 'EOF'
ANTHROPIC_API_KEY=sk-ant-your-key-here
MOLTBOT_LICENSE=adopt_abc123def456
PORT=3000
LOG_LEVEL=info
EOF

Use Docker Compose

Docker Compose makes it easy to manage one or more MoltBots with a single config file:

docker-compose.yml:

version: "3.8"

services:
  shellworth:
    image: ghcr.io/clickinclaws/moltbot-shellworth:latest
    container_name: shellworth
    restart: unless-stopped
    ports:
      - "3000:3000"
    env_file:
      - .env
    volumes:
      - shellworth-data:/data
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"

volumes:
  shellworth-data:

Start it up:

# Start in background
docker compose up -d

# View logs
docker compose logs -f shellworth

# Stop
docker compose down

# Update to latest version
docker compose pull && docker compose up -d

Auto-Start on Boot

Docker Desktop on Mac restarts containers automatically if you enable it:

Open Docker Desktop → Settings → General
Check "Start Docker Desktop when you sign in"
The restart: unless-stopped policy in docker-compose.yml handles the rest

Your Mac Mini will boot, start Docker, and your MoltBot will be running within a minute — no manual intervention needed.

4Deploy on a VPS

For 24/7 uptime without relying on your home network, deploy to a VPS. Any provider works — DigitalOcean, Linode, Hetzner, Vultr, etc.

Recommended Specs

1 MoltBot

1 vCPU, 1GB RAM
$5-6/month

2-5 MoltBots

2 vCPU, 2GB RAM
$10-12/month

5+ MoltBots

4 vCPU, 4GB RAM
$20-24/month

DigitalOcean Example

1. Create a Droplet (Ubuntu 24.04, $6/month):

# SSH into your new droplet
ssh root@your-droplet-ip

# Install Docker
curl -fsSL https://get.docker.com | sh

# Install Docker Compose plugin
apt-get install -y docker-compose-plugin

2. Set up your MoltBot:

# Create project directory
mkdir -p /opt/moltbots/shellworth
cd /opt/moltbots/shellworth

# Create .env file (use your actual keys)
cat > .env << 'EOF'
ANTHROPIC_API_KEY=sk-ant-your-key-here
MOLTBOT_LICENSE=adopt_abc123def456
PORT=3000
LOG_LEVEL=info
EOF

# Secure the .env file
chmod 600 .env

3. Create docker-compose.yml (same as Mac Mini above), then:

# Start your MoltBot
docker compose up -d

# Verify it's running
docker compose ps
curl http://localhost:3000/health

Optional: HTTPS with a Domain

If you want to access your MoltBot's dashboard from outside your network with HTTPS:

Add Caddy as a reverse proxy:

# docker-compose.yml (add this service)
services:
  caddy:
    image: caddy:2
    restart: unless-stopped
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile
      - caddy-data:/data
    depends_on:
      - shellworth

# Caddyfile
moltbot.yourdomain.com {
    reverse_proxy shellworth:3000
}

Point your domain's DNS A record to your VPS IP. Caddy handles SSL certificates automatically via Let's Encrypt.

5Running Multiple MoltBots

Collect them all? Run them all. Docker Compose makes this easy:

docker-compose.yml for multiple bots:

version: "3.8"

services:
  shellworth:
    image: ghcr.io/clickinclaws/moltbot-shellworth:latest
    container_name: shellworth
    restart: unless-stopped
    ports:
      - "3001:3000"
    env_file:
      - ./shellworth.env
    volumes:
      - shellworth-data:/data

  clawdia:
    image: ghcr.io/clickinclaws/moltbot-clawdia:latest
    container_name: clawdia
    restart: unless-stopped
    ports:
      - "3002:3000"
    env_file:
      - ./clawdia.env
    volumes:
      - clawdia-data:/data

  brobot:
    image: ghcr.io/clickinclaws/moltbot-brobot:latest
    container_name: brobot
    restart: unless-stopped
    ports:
      - "3003:3000"
    env_file:
      - ./brobot.env
    volumes:
      - brobot-data:/data

volumes:
  shellworth-data:
  clawdia-data:
  brobot-data:

Each MoltBot gets its own .env file with its own license key, and its own port. They share a single Anthropic API key (or use separate ones for billing isolation).

# Start all bots
docker compose up -d

# Check status of all bots
docker compose ps

# View logs for a specific bot
docker compose logs -f clawdia

# Update all bots
docker compose pull && docker compose up -d

6Connect to Claude Code or Claude Desktop

Every MoltBot includes an MCP (Model Context Protocol) server. This lets you use your MoltBot's tools directly from Claude Code or Claude Desktop.

Add to your Claude Code config (~/.claude/claude_desktop_config.json):

{
  "mcpServers": {
    "shellworth": {
      "command": "docker",
      "args": [
        "exec", "-i", "shellworth",
        "node", "openclaw/mcp-server/index.js"
      ]
    }
  }
}

Or if you extracted the adoption package locally:

{
  "mcpServers": {
    "shellworth": {
      "command": "node",
      "args": ["~/moltbots/shellworth/openclaw/mcp-server/index.js"]
    }
  }
}

After connecting, your MoltBot's tools appear in Claude's tool list. Claude can call your MoltBot to perform specialized tasks.

7Updating Your MoltBot

Developers can push updates to graduated MoltBots. When an update is available:

# Pull the latest version
docker compose pull

# Restart with the new version
docker compose up -d

# Verify it's running the new version
docker compose logs shellworth | head -5

Your data persists in the Docker volume, so updates don't lose your MoltBot's accumulated knowledge or configuration.

Troubleshooting

"License verification failed"

Check that MOLTBOT_LICENSE in your .env matches the license key from your collection page. Copy it fresh — spaces or newlines can break it.

"API key invalid"

Verify your Anthropic API key at console.anthropic.com. Make sure it's active and has available credits.

Port already in use

Change the host port in docker-compose.yml: "3001:3000" maps host port 3001 to container port 3000.

MoltBot using too much memory

Add memory limits in docker-compose.yml: deploy: resources: limits: memory: 512M

Container keeps restarting

Check logs: docker compose logs shellworth. Common causes: invalid .env values, missing API key, or a bug in the MoltBot (report it to the developer).

Cost Breakdown

Running a MoltBot has two ongoing costs:

Hosting

Free on your Mac Mini or existing computer. $5-24/mo on a VPS depending on how many bots.

Anthropic API

Pay-per-use based on how much your MoltBot thinks. Light usage: ~$1-5/mo. Heavy usage: $10-50/mo. You control the model and token limits.

What You Need

Docker — Your MoltBot ships as a Docker container. Install Docker Desktop (Mac/Windows) or Docker Engine (Linux/VPS).
An Anthropic API Key — Your MoltBot uses Claude as its brain. Get a key at console.anthropic.com. You pay for your own usage.
Your Adoption License Key — Found in your collection after adoption. This verifies you're the rightful owner.

1Quick Start (Any Machine)

The fastest path from adoption to running agent:

Pull and run your MoltBot:

# Pull the image
docker pull ghcr.io/clickinclaws/moltbot-shellworth:latest

# Run it
docker run -d \
  --name shellworth \
  -e ANTHROPIC_API_KEY=sk-ant-your-key-here \
  -e MOLTBOT_LICENSE=adopt_abc123def456 \
  -p 3000:3000 \
  ghcr.io/clickinclaws/moltbot-shellworth:latest

That's it. Your MoltBot is now running at http://localhost:3000.

Check that it's running:

# View logs
docker logs shellworth

# Check health
curl http://localhost:3000/health

# Stop it
docker stop shellworth

# Start it again
docker start shellworth

2Environment Variables

Every MoltBot accepts these environment variables:

Variable	Required	Description
ANTHROPIC_API_KEY	Yes	Your Anthropic API key. The MoltBot uses this to think.
MOLTBOT_LICENSE	Yes	Your adoption license key. Verified on startup.
PORT	No	Web dashboard port (default: 3000)
LOG_LEVEL	No	Logging verbosity: debug, info, warn, error (default: info)
DATA_DIR	No	Persistent storage path (default: /data). Mount a volume here.
MOLTBOT_MODEL	No	Override the Claude model (default: claude-sonnet-4-5-20250929)

Security: Never commit your API key or license key to version control. Use a .env file or your platform's secrets manager.

3Deploy on a Mac Mini

A Mac Mini is a great always-on home server for MoltBots. Here's the full setup from scratch:

Install Docker Desktop

# Install Homebrew if you don't have it
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

# Install Docker Desktop
brew install --cask docker

# Open Docker Desktop (needs to run in background)
open -a Docker

Wait for Docker Desktop to finish starting (whale icon in menu bar stops animating).

Create a Project Directory

# Create a home for your MoltBots
mkdir -p ~/moltbots/shellworth
cd ~/moltbots/shellworth

# Create your environment file
cat > .env << 'EOF'
ANTHROPIC_API_KEY=sk-ant-your-key-here
MOLTBOT_LICENSE=adopt_abc123def456
PORT=3000
LOG_LEVEL=info
EOF

Use Docker Compose

Docker Compose makes it easy to manage one or more MoltBots with a single config file:

docker-compose.yml:

version: "3.8"

services:
  shellworth:
    image: ghcr.io/clickinclaws/moltbot-shellworth:latest
    container_name: shellworth
    restart: unless-stopped
    ports:
      - "3000:3000"
    env_file:
      - .env
    volumes:
      - shellworth-data:/data
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"

volumes:
  shellworth-data:

Start it up:

# Start in background
docker compose up -d

# View logs
docker compose logs -f shellworth

# Stop
docker compose down

# Update to latest version
docker compose pull && docker compose up -d

Auto-Start on Boot

Docker Desktop on Mac restarts containers automatically if you enable it:

Open Docker Desktop → Settings → General
Check "Start Docker Desktop when you sign in"
The restart: unless-stopped policy in docker-compose.yml handles the rest

Your Mac Mini will boot, start Docker, and your MoltBot will be running within a minute — no manual intervention needed.

4Deploy on a VPS

For 24/7 uptime without relying on your home network, deploy to a VPS. Any provider works — DigitalOcean, Linode, Hetzner, Vultr, etc.

Recommended Specs

1 MoltBot

1 vCPU, 1GB RAM
$5-6/month

2-5 MoltBots

2 vCPU, 2GB RAM
$10-12/month

5+ MoltBots

4 vCPU, 4GB RAM
$20-24/month

DigitalOcean Example

1. Create a Droplet (Ubuntu 24.04, $6/month):

# SSH into your new droplet
ssh root@your-droplet-ip

# Install Docker
curl -fsSL https://get.docker.com | sh

# Install Docker Compose plugin
apt-get install -y docker-compose-plugin

2. Set up your MoltBot:

# Create project directory
mkdir -p /opt/moltbots/shellworth
cd /opt/moltbots/shellworth

# Create .env file (use your actual keys)
cat > .env << 'EOF'
ANTHROPIC_API_KEY=sk-ant-your-key-here
MOLTBOT_LICENSE=adopt_abc123def456
PORT=3000
LOG_LEVEL=info
EOF

# Secure the .env file
chmod 600 .env

3. Create docker-compose.yml (same as Mac Mini above), then:

# Start your MoltBot
docker compose up -d

# Verify it's running
docker compose ps
curl http://localhost:3000/health

Optional: HTTPS with a Domain

If you want to access your MoltBot's dashboard from outside your network with HTTPS:

Add Caddy as a reverse proxy:

# docker-compose.yml (add this service)
services:
  caddy:
    image: caddy:2
    restart: unless-stopped
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile
      - caddy-data:/data
    depends_on:
      - shellworth

# Caddyfile
moltbot.yourdomain.com {
    reverse_proxy shellworth:3000
}

Point your domain's DNS A record to your VPS IP. Caddy handles SSL certificates automatically via Let's Encrypt.

5Running Multiple MoltBots

Collect them all? Run them all. Docker Compose makes this easy:

docker-compose.yml for multiple bots:

version: "3.8"

services:
  shellworth:
    image: ghcr.io/clickinclaws/moltbot-shellworth:latest
    container_name: shellworth
    restart: unless-stopped
    ports:
      - "3001:3000"
    env_file:
      - ./shellworth.env
    volumes:
      - shellworth-data:/data

  clawdia:
    image: ghcr.io/clickinclaws/moltbot-clawdia:latest
    container_name: clawdia
    restart: unless-stopped
    ports:
      - "3002:3000"
    env_file:
      - ./clawdia.env
    volumes:
      - clawdia-data:/data

  brobot:
    image: ghcr.io/clickinclaws/moltbot-brobot:latest
    container_name: brobot
    restart: unless-stopped
    ports:
      - "3003:3000"
    env_file:
      - ./brobot.env
    volumes:
      - brobot-data:/data

volumes:
  shellworth-data:
  clawdia-data:
  brobot-data:

Each MoltBot gets its own .env file with its own license key, and its own port. They share a single Anthropic API key (or use separate ones for billing isolation).

# Start all bots
docker compose up -d

# Check status of all bots
docker compose ps

# View logs for a specific bot
docker compose logs -f clawdia

# Update all bots
docker compose pull && docker compose up -d

6Connect to Claude Code or Claude Desktop

Every MoltBot includes an MCP (Model Context Protocol) server. This lets you use your MoltBot's tools directly from Claude Code or Claude Desktop.

Add to your Claude Code config (~/.claude/claude_desktop_config.json):

{
  "mcpServers": {
    "shellworth": {
      "command": "docker",
      "args": [
        "exec", "-i", "shellworth",
        "node", "openclaw/mcp-server/index.js"
      ]
    }
  }
}

Or if you extracted the adoption package locally:

{
  "mcpServers": {
    "shellworth": {
      "command": "node",
      "args": ["~/moltbots/shellworth/openclaw/mcp-server/index.js"]
    }
  }
}

After connecting, your MoltBot's tools appear in Claude's tool list. Claude can call your MoltBot to perform specialized tasks.

7Updating Your MoltBot

Developers can push updates to graduated MoltBots. When an update is available:

# Pull the latest version
docker compose pull

# Restart with the new version
docker compose up -d

# Verify it's running the new version
docker compose logs shellworth | head -5

Your data persists in the Docker volume, so updates don't lose your MoltBot's accumulated knowledge or configuration.

Troubleshooting

"License verification failed"

Check that MOLTBOT_LICENSE in your .env matches the license key from your collection page. Copy it fresh — spaces or newlines can break it.

"API key invalid"

Verify your Anthropic API key at console.anthropic.com. Make sure it's active and has available credits.

Port already in use

Change the host port in docker-compose.yml: "3001:3000" maps host port 3001 to container port 3000.

MoltBot using too much memory

Add memory limits in docker-compose.yml: deploy: resources: limits: memory: 512M

Container keeps restarting

Check logs: docker compose logs shellworth. Common causes: invalid .env values, missing API key, or a bug in the MoltBot (report it to the developer).

Cost Breakdown

Running a MoltBot has two ongoing costs:

Hosting

Free on your Mac Mini or existing computer. $5-24/mo on a VPS depending on how many bots.

Anthropic API

Pay-per-use based on how much your MoltBot thinks. Light usage: ~$1-5/mo. Heavy usage: $10-50/mo. You control the model and token limits.

Deploy Your MoltBot

What You Need

1Quick Start (Any Machine)

2Environment Variables

3Deploy on a Mac Mini

Install Docker Desktop

Create a Project Directory

Use Docker Compose

Auto-Start on Boot

4Deploy on a VPS

Recommended Specs

DigitalOcean Example

Optional: HTTPS with a Domain

5Running Multiple MoltBots

6Connect to Claude Code or Claude Desktop

7Updating Your MoltBot

Troubleshooting

Cost Breakdown

Deploy Your MoltBot

What You Need

1Quick Start (Any Machine)

2Environment Variables

3Deploy on a Mac Mini

Install Docker Desktop

Create a Project Directory

Use Docker Compose

Auto-Start on Boot

4Deploy on a VPS

Recommended Specs

DigitalOcean Example

Optional: HTTPS with a Domain

5Running Multiple MoltBots

6Connect to Claude Code or Claude Desktop

7Updating Your MoltBot

Troubleshooting

Cost Breakdown