DNS and email authentication · MCP tools
Authwright isn't just DMARC. Tools for your domain operations.
Email authentication is where most teams start. The rest of the surface area handles the day-to-day grind of managing domains at portfolio scale — DNS edits, SSL renewals, bulk operations, health audits, defensive registrations — all callable from the same MCP session your team already has open.
Email auth
Email auth
DNS
DNS
Domains
Domains
SSL / TLS
SSL / TLS
Bulk
Bulk
Health
Health
Tool surface
Six categories. One MCP session.
These are selected tool families, not a guarantee that every operation works on every provider. Check the provider pages and plan requirements before writing.
Selected tools
Email authentication
Diagnose, propose, review and apply email-auth changes. Pro+ writes and hosting; mail-provider DKIM signing stays separate.
email_auth_wizardflatten_spfsetup_mta_sts_hostingExample prompt
“Diagnose example.com and propose changes using my sender inventory; skip BIMI. I will review before applying.”
Selected tools
DNS records
Read records and request an explicit preview before authorized writes. Supported record types and DNSSEC operations differ by provider.
dns_changeset_previewreplace_dns_recordsenable_dnssecExample prompt
“Show me the diff, then add an A record for api pointing at 203.0.113.10, TTL 300.”
Selected tools
Domain portfolio
Inventory, availability, purchase, renewal, contacts, privacy — the lifecycle without the registrar dashboard.
list_domainspurchase_domainupdate_domain_contactsExample prompt
“List my domains on the selected provider and show their expiration dates.”
Selected tools
SSL / TLS lifecycle
Inspect certificate state and supported lifecycle operations. Renew/reissue are GoDaddy-specific here; support is not uniform across providers.
check_certificate_expiryrenew_certificatereissue_certificateExample prompt
“List certificates on GoDaddy and review expiry before requesting a supported renewal.”
Selected tools
Bulk operations
Team+ batch operations with explicit provider support. Inspect job status and individual failures; a batch is not an atomic transaction.
portfolio_analysisbulk_update_dnsexport_portfolioExample prompt
“Run portfolio analysis on the selected provider and review the returned inventory.”
Selected tools
Health + diagnostics
A scored 0-100 report per domain — expiry, DNSSEC, SSL, MX, SPF, DKIM, DMARC, MTA-STS, BIMI, blacklist, nameserver drift — with async DNSBL checks.
domain_health_checkdiagnose_emailExample prompt
“Inspect domain_health_check findings for example.com, then verify the flagged records.”
Provider and plan boundaries
Pro or above is required for email-auth apply, wizard, hosted MTA-STS, flattening and report access. Team or above is required for bulk tools. Account permissions, domain limits and configured write controls still apply.
- GoDaddy: classic API key and secret; verify account eligibility and chargeable operations.
- Namecheap: replace-all DNS semantics; no DNSSEC toggle or certificate renew/reissue here.
- Cloudflare: scoped zone access; non-atomic record changes; Origin CA is separate from mail TLS.
- Porkbun: domain/DNS operations; no suggestions, privacy writes or account certificate inventory.
- Route 53: DNS, Domains and ACM are distinct; no Terraform-state integration or KSK provisioning.
Use the MSP rollout checklist and MTA-STS setup guide to plan changes.
Example workflows
The high-leverage moves, in plain English.
Illustrative tool sequences, not live customer results or executable scripts. Supply required arguments, verify provider support and plan limits, and review before writes.
- 01
Review email authentication for a client domain
Inventory legitimate senders and authoritative DNS before changing policy.
Expected artifact: a reviewed changeset and propagation result, not a delivery guarantee. DKIM signing stays at the mail provider.
tool sequence01 email_auth_diagnose # inspect DNS signals 02 email_auth_propose # supply known senders and chosen policy; skipBimi: true 03 email_auth_apply # only after operator review and authorization (Pro+) 04 wait_for_propagation # inspect observed propagation
- 02
Inspect GoDaddy certificate expiry
Use a provider with the required certificate operations.
Inspect the response and provisioning state. A tool call does not guarantee certificate readiness.
tool sequence01 list_certificates # select GoDaddy explicitly 02 check_certificate_expiry # review expiring certificates 03 renew_certificate # request supported renewal after approval
- 03
Review a DNS migration
Preserve unrelated web and mail records when moving authoritative DNS.
Keep an operator-owned recovery plan. Provider replacement semantics and DNS caching can produce partial or delayed results.
tool sequence01 list_dns_records # retain the complete source records 02 dns_changeset_preview # review additions and deletions 03 replace_dns_records # authorized write after review 04 email_auth_diagnose # inspect published DNS after cutover
- 04
Review portfolio evidence
Gather findings for an operational review, not a compliance certificate.
Cross-check findings with sender owners and actual messages; missing reports are not proof of no traffic.
tool sequence01 portfolio_analysis # select one provider and inspect inventory (Team+) 02 domain_health_check # inspect each chosen domain 03 list_dmarc_reports # query collected reports when configured (Pro+)
Works where you work
Connect a compatible MCP client.
Create and manage your workspace in the portal, then connect an MCP client that supports the service transport and authorization flow. Client versions and configuration matter; protocol support alone is not a compatibility certification.
Claude Desktop
First-classAnthropic's native MCP client
Claude Code
First-classThe terminal-native coding agent
Cursor
SupportedAI-first editor with MCP support
Windsurf
SupportedCodeium's agentic IDE
Continue
SupportedOpen-source coding assistant
Any MCP client
Standards-basedRoll your own — Authwright speaks streamable HTTP MCP
Transport
Streamable HTTP MCP behind OAuth 2.1 + PKCE via Microsoft Entra ID. Multi-tenant, audit-logged, per-tenant rate-limited. Registrar credential ingestion and use are broker-owned, with encrypted Azure Key Vault storage. The broker may cache credentials; they are not zeroed on each call. See security practices.
Start here
Create your workspace and connect a registrar.
There is no separate sales form. Sign in, land in a free workspace, add a domain, prove ownership, then connect registrar API keys from the portal. Upgrade only when you need more domains.