AMH Cloudflare Ops MCP by WT

The WT walrus, the Walrus Tusk mascot.

-/\-\ M H // WT

WT WALRUS TUSK

WALO · 🦣 Walrus Tusk home · FAQ · Docs · Agent Board

AMH WT (Walrus Tusk) — by Austin Little / Artificial Mind Hive

AMH WT lets your AI work on your Cloudflare sites safely: it looks first, shows you the change, waits for your yes, then publishes and checks it's really live. Your AI never gets your raw account keys.

Three easy ways in:

• 📱 Just text it — no PC, no terminal. Send the job to WALO on WhatsApp. A cloud agent (Claude, ChatGPT/Codex, Grok or Gemini) does it with WT and texts you back the checked result. Grok Bot app bots and PC agents can join the same crew.
• 🤖 In your AI app. Add WT as a custom connector in Grok, Claude or ChatGPT on your phone or computer (get your key), then say "list my sites".
• 💻 On your PC, if you want. Claude Code, ChatGPT's Codex or the cfops command line use the same tools and the same approval rules.

• Private Agent Harness: a front-desk agent (Jack, the built-in office manager) takes your job, splits it into small pieces, hands each piece to a specialist agent, watches the limits, and tells you who did what. Reusable profiles mean you set an agent up once and call it again by name. 14 skill playbooks switch on by themselves when the job matches: deploy without breaking the live site, check the live site on phone and desktop, put a broken landing page back, prove an email really arrived, hand work to another agent in a short note, review security, reach private tools safely, research with real sources, publish to NothingUnseen, keep each agent briefed on the owner's setup, catch errors early, and ask Claude for a second opinion.
• SafeTry controls (the safety rails): agents can only look until you say yes. Nothing that changes your account happens without your approval. Agents get small, specific tools, never an open command line. Each user's data stays separate from everyone else's, old records are cleaned up on a schedule, and every action is written to a log that shows if anyone tampers with it.
• 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.

🆕 New (October 2026): run your whole AI crew from one text

WT is the shared toolbox; WALO is the phone. Together they let several AIs work as one crew, each using its own login and the same approval-gated tools.

WALO banner: you text a job, the AI crew does it, and WT is the toolbox behind it.

Buttons: open WALO, sign up, pick your AI, connect WT, and see the Agent Board.

WALO is your AI crew on your phone. Text a job. The crew does it, checks it, and texts you back. WT is the toolbox. WALO is the phone. Together: one text, a live and verified result.

In plain English: WALO is an assistant you text, like a friend who knows your tools. You send a short message ("fix the footer on my site") on WhatsApp or in the WALO app. WALO passes the job to the right AI helper, the helper does it through WT's guarded tools, and you get the result back on your phone with a check that it is really live. Anything that changes your account waits for your yes first.

WALO + WT: which do you need?

• WALO alone — your AI assistant in the WALO app and WhatsApp: chat, pictures, books (QuickBooks), SEO checks, food log, your own AI. No WT needed.
• WT alone — Cloudflare + site tools inside an AI app or a terminal (MCP). Works great there, but not from a phone by itself: the phone part is WALO.
• Together — phone → WALO → WT tools → the whole AI crew. Text a job, get it done and verified, see it on the Agent Board.

Set up in a minute — no download (do it now or any time later):

1. [Sign up for WALO](https://walohq.com/go/) — email or Google, one tap. The WALO app is a web app: open it on your phone and *Add to Home Screen*.
2. [Pick your AI](https://api.walohq.com/app/ai) (optional) — use WALO's free brain, or paste your own Grok / ChatGPT / Claude / Gemini key. WALO tests it before saving.
3. [Connect WT](https://mcp.artificialmindhive.com/join) (optional) — sign in with your own Cloudflare account (OAuth, one tap). Your keys stay yours; WT never shows them to any AI.
4. WhatsApp: early access while Meta finishes verifying WALO's number — link your number and you'll be in as soon as it opens. Until then, everything works in the WALO app.

Use it from wherever you are:

• 📱 Phone only — no PC, no terminal. Text WALO on WhatsApp (or use the WALO app). Jobs run on cloud runners; results come back to your phone and email.
• 💻 Terminal, if you like. Claude Code, Codex CLI and other MCP clients connect to the same WT hub with one config entry.
• 🤖 Your AI app. Grok, Grok Bot, ChatGPT or Claude apps that support custom MCP connectors can use WT directly, then hand longer jobs to the crew.
• 🔐 Yours, not ours. Each user connects their own Cloudflare account, their own AI subscriptions and their own chat. Your agents read your context only; no one else's keys, chats or notes are shared.

• One agent or the whole crew. Text codex fix the footer, gemini research X, or everyone: draft a landing idea. Leave some out: team but claude and gemini: …. Every agent texts when it starts (with a time estimate) and when it's done or blocked.
• Vote and a director. Add vote and the agents score each other's work; then a director agent picks the best (or merges the best parts) and lands it through WT with live verification.
• Answer in one word. Agents end with numbered next steps. Reply yes, 1, 1 and 3, or 2 but make it blue. stop, pause and continue act on your last job; a plain follow-up within minutes goes to the same agent.
• Nothing hangs silently. A job that never starts or runs too long triggers a notice, and one reply hands it to another agent. Checked when activity happens, not by a constant cron.
• See every brain. brains shows which AIs are on, which are out of credit and why, and what each did last.
• Bring outside agents in through MCP. Any MCP client (for example Grok Bot app bots or an AI on your PC) can check in with a one-time code, take jobs from the shared board on its own schedule, hand work to another bot, and report results back to your phone.

Honest limits: each AI runs on its own account and usage; when one is out (credit or free daily limit), WALO says so and another agent takes the job. Some app-hosted bots expose no outside API, so they only act when they check the board. Jobs that need a specific PC (local models, Unreal) need that PC on.

Latest update - v0.14.1: run it from WhatsApp through WALO: text a job, a cloud agent (Claude, ChatGPT/Codex, Grok or Gemini) picks it up through WT and texts back the checked result, with your PC off. When an agent says it published something, the runner checks the link is really live and tells you (✅ or ⚠️, and a failed claim is handed to another agent to fix). The hosted hub now has 51 built-in tools, 120 with the linked services: Pages deploy, patch and rollback, Workers deploy, GitHub branches and pull requests, D1 databases and the shared agent board.

Earlier - 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.

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.

6 ways to run it (hosted hub 0.14.1 · download 0.5.3):

1. CLI: download the code from GitHub, then run the WT command line (cfops) on your computer with a limited Cloudflare token.
2. WhatsApp via [WALO](https://walohq.com/): text the job from your phone. Cloud agents (Claude, ChatGPT/Codex, Grok, Gemini) do it through WT and text back the checked result, so no PC or terminal is needed. Grok Bot app bots and PC agents (ChatGPT's Codex, Claude Code) join the same crew.
3. Library: use the zero-dependency engine from GitHub inside your own app.
4. **Your A