Marketplace for trusted AI agent skills

Deploy OpenClaw on Cloudflare Workers with Moltworker

Skill Detail

Deploy OpenClaw on Cloudflare Workers with Moltworker

Use Moltworker to deploy a supervised OpenClaw personal agent stack on Cloudflare Workers, Sandbox containers, Access, R2, and optional AI Gateway.

Templates & WorkflowsOpenClaw
Templates & Workflows OpenClaw Security Reviewed
⭐ 9.9k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill deploy-openclaw-on-cloudflare-workers-with-moltworker Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
View source Documentation
At a glance
Tools required
Cloudflare Workers Paid plan, Wrangler, Cloudflare Sandbox containers, Cloudflare Access, model provider or Cloudflare AI Gateway credentials, optional R2 Storage
Install & setup
Clone the Moltworker repository, run npm install, set the required Wrangler secrets for the model provider and gateway token, deploy with npm run deploy, then configure Cloudflare Access, device pairing, and optional R2 persistence.
Author
Cloudflare
Publisher
Organization
Last updated
May 18, 2026
Quick brief

Use Moltworker when an operator wants to run OpenClaw as an always-on personal assistant on Cloudflare’s edge platform instead of maintaining a VPS. The workflow is to install dependencies, set provider and gateway secrets with Wrangler, deploy the Worker and Sandbox container, protect the admin UI with Cloudflare Access, pair approved devices, and optionally enable R2 persistence, browser automation, and AI Gateway routing.

How it works

What this skill actually does

Invoke this when the goal is a managed OpenClaw deployment with explicit authentication, device pairing, persistence choices, and Cloudflare-native operations. The scope boundary is the Cloudflare Workers deployment runbook for OpenClaw, not generic Wrangler usage, the full Cloudflare platform, or OpenClaw agent design.

Inputs are a Cloudflare Workers paid account, provider or AI Gateway credentials, a generated gateway token, Access configuration, and optional R2 and browser automation settings. Outputs are a deployed OpenClaw gateway URL, protected admin UI, paired devices, persistent configuration, and an operations checklist another maintainer can audit.