An approval-gated Cloudflare operations suite with an optional private Agent Harness: bounded delegation, deterministic verification, OAuth-isolated MCP tools, and verified deploy checks without handing agents raw account credentials.
·Private Agent Harness: Jack, the built-in front-desk agent, takes your job, splits it into small pieces for specialist agents, watches the limits and tells you who did what. Set an agent up once as a reusable profile and call it again by name. 14 skill playbooks switch on by themselves when a job matches: safe deploys, live checks on phone and desktop, landing rollback, mail loopback, lean handoffs, security review, private MCP access, Google source research, optional Claude second opinions and more.
·SafeTry controls: read-only defaults, explicit approvals, narrow adapters instead of a generic shell, tenant isolation, retention limits, and a tamper-evident audit chain.
·Verified deploy gate: checks the public target for an explicit 2xx status, rejects redirects, and optionally requires an expected release marker before reporting success.
·Deterministic site health: zero-AI HTTP checks remain useful for small valid pages and can require an expected text marker to catch a 200 response serving the wrong site.
·Self-catching email loopback: exercises the configured sending/routing path and records delivery evidence; it does not claim to prove placement in a provider's inbox tab.
·Cloudflare-native connections: optional OAuth connectors for the official Cloudflare API, Workers Builds, Bindings, Observability, and Docs MCP services, plus Wrangler-based Worker deployment and secrets.
·Guarded operations: Turnstile, DNS, SPF/DMARC/BIMI, Email Routing, Pages cutovers, cache purge, scoped tokens, and account diagnostics stay dry-run or approval-gated where they write.
Latest update - v0.4.2: the live harness now selects reusable skill folders automatically, shows them in the operator console, records them in hashed job packets, supports Google-first source research and an optional user-configured Claude verification pass, and targets learned improvements at reviewable skill revisions. See the latest release.
AMH WT scans Cloudflare configuration, computes a diff of desired vs current DNS / Email Routing / BIMI / DMARC / SPF / Pages / cache / Turnstile setup, and applies fixes only after explicit approval. It is built for people who want an AI agent to help with Cloudflare safely: scan first, show the plan, then write only when the owner approves.
Version 0.14.1 works 6 ways
·CLI: run the WT command line (cfops) locally with a scoped Cloudflare token.
·Library: import the zero-dependency engine into your own app.
·Hosted OAuth MCP: connect your own Cloudflare account and receive a one-user cfops_ connector key. The owner's API token is never shared.
·Self-hosted MCP Worker: deploy the included Worker with Wrangler for your own team or infrastructure.
·Private Agent Harness: deploy the companion agent/ Worker behind the MCP Worker's AGENT_HARNESS service binding for bounded jobs, health watches, schedules, audit, and the authenticated operator console.
For repository-connected deployments, see GIT-INTEGRATION.md. The recommended route uses Cloudflare Workers Builds' GitHub App authorization; the MCP does not store a GitHub token.
AMH WT is especially useful for Cloudflare operators who need repeatable DNS hygiene across many zones: SPF cleanup, DMARC enforcement, BIMI records, MX checks, DKIM discovery, Cloudflare Email Routing, TXT verification records, safe DNS upserts, and audit logs for every approved write.
Unofficial Cloudflare tool. AMH WT is made by AMH - Artificial Mind Hive, operated by Service Pricer LLC. It is independent, third-party, open-source software. It is not affiliated with, endorsed by, sponsored by, or made by Cloudflare, Inc. "Cloudflare" and "Wrangler" are referenced only to describe compatibility with Cloudflare's platform and official developer tooling. You are responsible for every DNS, Email Routing, DMARC, BIMI, SPF, or Worker change you approve and apply.
No owner's API key in Git or in your client. Public users authorize Cloudflare directly. OAuth access and refresh tokens stay server-side in KV; the connector key is stored only as a SHA-256 hash and is bound to one OAuth grant.