Cloudflare DNS, from your MCP client. Know the zone boundary.
Use Authwright to inspect and manage supported Cloudflare DNS operations from an MCP client. Built for domain owners, MSPs and agencies who need explicit provider scope, reviewed changes and useful diagnostics.
Use a scoped Cloudflare API token with access to the intended zone and operations. The broker resolves the zone ID from the domain.
list_dns_records for example.com, provider cloudflareIllustrative response: current record setemail_auth_diagnose for example.comReview DNS findings and mail-provider inputsPropose changes; review before authorized apply
- GoDaddy
- Namecheap
- Cloudflare
- Porkbun
- Route 53
BEFORE YOU CONNECT
Where does Cloudflare fit in your email setup?
Confirm Cloudflare is authoritative. Mail-server host records must be DNS-only when used for SMTP; the ordinary HTTP proxy does not proxy SMTP.
Use a scoped Cloudflare API token with access to the intended zone and operations. The broker resolves the zone ID from the domain.
“Registrar, authoritative DNS host and mail sender can be three different services.”
SELECTED MCP TOOLS
Practical Cloudflare DNS workflows.
Record replacement is a sequence of per-record changes, not an atomic transaction. Cloudflare Origin CA certificates are not public mail transport certificates.
list_dns_records()Read the current records on the selected supported provider. Confirm the domain and authoritative DNS host first.dns_changeset_preview()Request a diff before a write. Preview is an explicit tool call, not an automatic confirmation screen for every operation.add_dns_records()Publish caller-supplied records after review and authorization. DKIM public records come from the mail provider; signing is enabled there.email_auth_diagnose()Inspect published email-auth signals, including common DKIM selectors. This does not test inbox placement or prove message alignment.email_auth_propose()Prepare a changeset using explicit sender and policy inputs. Review each operation; omit BIMI until its real logo and certificate prerequisites are satisfied.email_auth_apply()Apply an approved changeset with the required authorization and paid tier. Preserve a recovery plan and check the actual result.setup_mta_sts_hosting()Pro and above: managed HTTPS policy hosting. DNS validation and certificate provisioning must complete before relying on enforcement.
Workers, R2, Pages and Access are outside this tool surface. A common MCP vocabulary does not mean every Cloudflare product is supported.
Plan the email-auth rollout
Start with the MSP sender inventory and rollout checklist, then review MTA-STS DNS and HTTPS setup. See tool and plan boundaries before authorizing changes.
MCP, not SaaS
If your team lives in Claude, Cursor, or ChatGPT, this is the tool your stack was missing.
Authwright is built as a Model Context Protocol server — which means it's callable directly from the AI environments your operators already use.
Use the portal to create a workspace, prove domain control and connect a provider. Then configure your MCP client for authorized DNS operations.
Read and propose before applying changes. Tool authorization does not replace an operator reviewing sender inputs, provider limits and recovery steps.
> Diagnose email authentication for example.com. 1. email_auth_diagnose: inspect published DNS signals 2. email_auth_propose: supply sender inputs; skipBimi: true 3. Operator reviews the proposed record changes 4. email_auth_apply: authorized write (Pro+) 5. wait_for_propagation: inspect observed results DKIM signing stays with the mail provider.
What makes it different
Checks before you change DNS.
- 01CREDENTIALS
Connect the right account.
Use a scoped Cloudflare API token with access to the intended zone and operations. The broker resolves the zone ID from the domain.
- 02DNS_OWNER
Review the authoritative records.
Confirm Cloudflare is authoritative. Mail-server host records must be DNS-only when used for SMTP; the ordinary HTTP proxy does not proxy SMTP.
- 03SUPPORT
Check the operation boundary.
Record replacement is a sequence of per-record changes, not an atomic transaction. Cloudflare Origin CA certificates are not public mail transport certificates.
- 04VERIFY
Inspect the result.
Workers, R2, Pages and Access are outside this tool surface. A common MCP vocabulary does not mean every Cloudflare product is supported.
Self-service setup
From workspace to reviewed DNS changes.
- 01
Create a workspace.
Sign in with Google, Microsoft or a magic link. Start on the ongoing Free tier; no password or automatic timed-pilot conversion.
- 02
Prove domain control.
Choose an authorized domain from your own Cloudflare zones. Complete the domain-proof step in the portal.
- 03
Connect your provider.
Submit scoped credentials through the broker-owned connection flow. Check provider eligibility and supported operations.
- 04
Configure MCP and review.
Connect your client, inspect DNS and propose changes. Upgrade for paid operations when needed; authorize writes deliberately.
Pricing
Priced for the way developers actually work.
Free diagnosis is a starting point. Pro adds email-auth writes and managed hosting; Team adds bulk tools. Provider and account support still apply.
Free public audit
Start with published email-auth DNS.
Drop any domain into our free checker. We'll show you the current DMARC policy, top-level SPF terms, common DKIM selectors, MTA-STS TXT and MX. The grade is a DNS heuristic, not a delivery guarantee. No login. No email gate. No upsell pop-up.
FAQ
Cloudflare setup and operation limits.
Technically accurate against the broker's capability matrix. If something is unsupported: today, we say so here.
- Use a scoped Cloudflare API token with access to the intended zone and operations. The broker resolves the zone ID from the domain.
- Connect the authoritative DNS provider, not necessarily the domain registrar. If Authwright does not support that DNS provider, publish the records through that provider controls.
- Record replacement is a sequence of per-record changes, not an atomic transaction. Cloudflare Origin CA certificates are not public mail transport certificates.
- No. The wizard is write-capable when invoked with the required inputs and authorization. For preview-first work, call diagnosis and proposal separately, review the changeset, then authorize apply.
- No. DNS publication is one part of email authentication. Obtain the public DKIM record and enable signing at your mail provider. Check actual message headers and reporting before tightening DMARC.
- Yes. The supported brands are GoDaddy, Namecheap, Cloudflare, Porkbun and Route 53. Select the provider explicitly for account inventory. Operation support, credentials and plan limits differ.
- Workers, R2, Pages and Access are outside this tool surface. A common MCP vocabulary does not mean every Cloudflare product is supported.
Q1What credentials and access do I need?
Q2My domain is registered here, but DNS is elsewhere. Which connection matters?
Q3Does every tool work on this provider?
Q4Will the wizard wait for a separate approval dialog?
Q5Can this guarantee delivery or configure DKIM signing?
Q6Can I use more than one provider?
Q7What should I verify after a change?
Pilot
Try it on your own zones.
Tell us about your setup; we'll reply within one business day.
Already convinced? Skip the form and start free.