MoltenRock Connect · the Human Queue for Cloudflare · live

Your agent runs Cloudflare. You approve every change.

Your AI agent reads over eighty kinds of Cloudflare data and proposes the work: DNS records, HTTPS and security settings, firewall rules, Pages and Workers changes. Each card waits in your Human Queue until you approve it with Touch ID. Then MoltenRock Connect sends it. The agent never holds a write token.

Free download · approving needs MoltenRock Pro · works with Claude Code, Claude Desktop, Cursor, Codex and OpenClaw
Human Queue · Cloudflare4 sites
Claude Code proposes
Always HTTPS · TLS 1.2+
example.com, shop.example.com and 2 more
Now
Plain HTTP answered; TLS 1.0 accepted.
Will be
Every visit on HTTPS; TLS 1.2 or newer.
Prompted by
“Harden every site we run on Cloudflare.”
Deny with a noteApprove with Touch ID

Waiting for you · expires in 72 h if nobody decides

Illustration, example data.

How it works

Your agent does the work. You make the call.

The same four steps for every change, whether it’s one DNS record or HTTPS on every site you run.

  1. 01
    Your agent reads
    Sites, DNS, analytics, rules, Workers and more, through one local connection. The token stays in your Mac’s Keychain or MoltenRock’s vault.
  2. 02
    It proposes a change
    A card in your Human Queue: what it wants to change, on which sites, and why, with the value now next to the value it will be.
  3. 03
    You approve with Touch ID
    Or deny it with a note your agent reads back. Connect reads Cloudflare fresh first, and sends nothing for a value that has changed since.
  4. 04
    Connect sends it
    Straight from your Mac to Cloudflare, logged on your Mac. Undo is one card away.

Live · 83 kinds of change

What your agent can propose.

Each one on its own card, checked against Cloudflare before it’s sent.

  • Security & site settings
    HTTPS and TLS settings, HSTS, bot protection, managed security headers, DNSSEC, security.txt, cache purges; settings on up to 25 sites at once.
  • DNS
    Add, change or remove DNS records, and add a site to Cloudflare.
  • Firewall & rules
    IP rules, firewall, rate-limit and skip rules, managed WAF rules, redirects, header and cache rules.
  • Email Routing
    Turn it on, add forwarding addresses and routes, and choose what happens to everything else.
  • Pages sites
    Create a site from a GitHub repository, set its build, variables, secrets and domains, deploy, retry, roll back.
  • Workers
    Versions and gradual rollouts, routes, domains, variables, secrets, schedules, logs and builds.
  • Storage
    Workers KV, R2 buckets (public address, CORS) and D1 databases: create, run SQL, restore.
  • Access
    Put a login in front of a staging or admin address, and choose who gets in.
  • And more
    Turnstile bot checks, notifications, Web Analytics, Tunnel routes, load-balancer pools.

Not yet: uploading a Pages site’s files or a Worker’s static assets straight from your Mac. Deploy those from a connected GitHub repository instead.

Built to be safe

Every card tells you what you’re approving.

  • Now, and what it will be
    Each card shows the setting as it is now, read fresh from Cloudflare before you approve, next to what it will become. A value that changed since isn’t sent.
  • Several sites, one card
    One card can change the same settings on up to 25 sites. You see each site’s result, step by step.
  • Undo is a new card
    After a change, Undo files a card that puts back what was there. You approve it like any other.
  • Warnings in plain words
    “Mail stops arriving”, “Hard to take back”, “No Undo”: risky changes say so on the card before you approve.
  • Secrets typed by you
    A Worker or Pages secret’s value is typed by you, on the card. Your agent never sees it and Connect doesn’t keep it.
  • Gone after 72 hours
    A card nobody decides on expires after 72 hours and nothing is sent. Deny with a note and your agent can try again.

Reads, as before

Read access, without handing over the token.

  • Over eighty reads
    Sites, DNS records, analytics and more, through one local connection your agent already knows.
  • The token stays put
    In your Mac’s Keychain or MoltenRock’s Secure-Enclave vault. Your agent never receives it.
  • Every request logged
    One line per call in Connect’s audit log, on your Mac. A kill switch refuses everything at once.
  • Touch ID for changes
    Approve and deny exist only in the app, behind Touch ID. Your agent has no way to approve its own card.

What’s next

Hear when the next platform lands.

The Human Queue works with Stripe, Cloudflare and GitHub today. One email when it adds the next platform.

Human Queue news only, when it adds a platform. Unsubscribe anytime. Privacy

Questions

Cloudflare and your agent

Can my agent change anything in Cloudflare on its own?

No. It can read, and it can propose. Nothing changes in Cloudflare until you approve the card with Touch ID in MoltenRock Connect; Connect then sends it with the token it holds. Your agent never receives a write token.

What can it propose?

83 kinds of change today: site and security settings, DNS, firewall and rules, Email Routing, Pages, Workers, KV, R2, D1, Access, Turnstile, notifications and more. Not yet: uploading a Pages site’s files or a Worker’s static assets straight from your Mac. Cloudflare takes those only with a short-lived upload token and a many-file upload, which Connect doesn’t build yet.

Which Cloudflare token should I use?

A read-only API token is enough for reads. For changes, give Connect a token with the write permissions you’re happy to allow; if a card needs a permission the token doesn’t have, the card names it in Cloudflare’s words. The token stays in your Mac’s Keychain or MoltenRock’s vault and is never shown to your agent.

What about secrets for my Workers and Pages sites?

Your agent proposes the secret’s name; you type its value on the card. The agent never sees it, and Connect sends it to Cloudflare without keeping it.

Can I take a change back?

For most cards, yes: once a change is done, Undo files a new card that puts back what was there before, and you approve it like any other. Cards that can’t be undone (running SQL on a D1 database, for one) say “No Undo” before you approve.

Does anything go through a MoltenRock server?

No. Connect calls Cloudflare’s API directly from your Mac, and your agent talks to Connect on your Mac. Every request and every decision is logged locally.

What does it cost?

MoltenRock Connect is free to download and covers a couple of platforms for free; Cloudflare can be one of them. Approving Human Queue cards needs MoltenRock Pro ($9.99/month or $99.99/year), which also unlocks every Connect platform.

Let your agent do the Cloudflare work. You keep the last word.

Free to download. Keep your Cloudflare token out of your agent’s config.