AMH Cloudflare Ops MCP by WT MCP server

-/\-\ 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.

Shortened. The full README is on GitHub.