-/\-\ M H // WT

_{WT WALRUS TUSK}

🦣 Walrus Tusk home · FAQ · Docs

AMH Cloudflare Ops MCP by Walrus Tusk (WT)

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-friendly reusable profiles plus 14 automatic process skill folders for safe deploys, live checks, landing restore, mail verification, lean handoffs, security review, private MCP access, source research, NU publishing, operator context, error detection, and optional Claude second opinions.
• 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.5.3: the owner-supplied WT Connected OAuth setup UI is now the only success-page renderer. Every release runs it in Chromium under the production security policy and verifies the WT/AMH identity, all four copy controls, phone layout, images, and legacy-link removal. See the latest release.

Cloudflare Ops MCP 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.5.3 works five ways:

• CLI: run 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 at console.artificialmindhive.com/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.

Machine discovery is available at robots.txt, sitemap.xml, llms.txt, and walrus-tusk.md. These describe the public landing and documentation; authenticated MCP and OAuth callback routes remain excluded from crawling.

Cloudflare Ops MCP 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. Cloudflare Ops MCP 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.

What Cloudflare Ops MCP handles

Cloudflare Ops MCP is focused on the Cloudflare tasks that regularly break launches, email trust, bot checks, cache freshness, brand display, and AI-agent workflows:

• DNS record scan, lookup, create, update, no-op detection, and guarded delete.
• SPF detection and planning so you do not accidentally create multiple SPF records.
• DMARC parsing and policy updates that only change the fields you asked for.
• BIMI TXT setup with a DMARC enforcement gate.
• DKIM discovery so the report can tell whether sender keys exist.
• MX and Cloudflare Email Routing checks.
• Email Routing destination/rule setup with verified-destination protection.
• Audit logs for applied changes.
• Cloudflare Pages DNS cutovers and cache purge operations.
• Turnstile widget planning/creation for bot checks.
• MCP endpoint deployment on Cloudflare Workers with Wrangler secrets.
• AI-agent safety defaults: dry-run first, diff display, no token in tool args, no accidental deletes.

This is not meant to replace every Cloudflare feature. It is the narrow, safe lane for common Cloudflare ops an operator or AI agent should be allowed to do.

Examples are operator recipes

The examples below are intentionally direct. They are not toy examples. They show the exact dry-run -> review -> apply pattern users should follow when fixing real domains.

Cloudflare Pages DNS cutover

Use this when an old registrar, parking page, Vercel app, HugeDomains page, or stale A/AAAA records are blocking a Cloudflare Pages custom domain.

Dry-run first:

cfops pages example.com --target project.pages.dev

Apply only after reviewing the delete/create plan:

cfops pages example.com --target project.pages.dev --apply

What it changes:

• Deletes conflicting apex A/AAAA/CNAME records.
• Deletes conflicting www A/AAAA/CNAME records and www NS delegations.
• Adds proxied CNAME records for apex and www pointing at the Pages target.
• Leaves TXT, MX, SPF, DKIM, DMARC, BIMI, and other delegated subdomains alone.
• Leaves wildcard records alone unless you explicitly add --wildcard.

Options:

• --no-www only cuts over the apex domain.
• --wildcard also removes conflicting *.example.com A/AAAA/CNAME records.

Why build this with Wrangler?

Wrangler is Cloudflare's official developer CLI. Cloudflare Ops MCP can run without Wrangler as a local CLI/library, but Wrangler is the right path when you want a remote MCP server because it deploys the Worker, stores secrets, tails logs, and manages Cloudflare bindings from the same toolchain Cloudflare documents.

Use Wrangler when you want:

• a hosted MCP endpoint for agents and teammates;
• server-side OAuth client secrets and optional private admin fallback secrets;
• Cloudflare Pages/Workers deployment checks;
• observability through Cloudflare logs;
• a repeatable production setup instead of local-only scripts.

Use the plain CLI when you only need one local terminal to scan or fix a zone.

Current release notes

Safety model (the whole point)