Plan, apply, verify and roll back SPF, DKIM, DMARC and MX for cold email domains on Cloudflare
MCPpedia last refreshed this data
io.github.anasmughal239-alt/domain-setup-mcp is an MCP server that plan, apply, verify and roll back SPF, DKIM, DMARC and MX for cold email domains on Cloudflare. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 61/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"domain-setup": {
"env": {
"CLOUDFLARE_API_TOKEN": "your_token"
},
"command": "domain-setup-mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Plan, apply, verify and roll back SPF, DKIM, DMARC and MX for cold email domains on Cloudflare
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
uvx 'domain-setup-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked domain-setup-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in cloud / communication
Official TypeScript library for the Telnyx API
Gives AI development tools Firebase-specific capabilities and expertise.
Cloud-powered AI platform with multi-agent swarms, sandboxes, and workflow automation
Send email and newsletters with Mailtea over MCP, plus skills for email and website design.
MCP Security Weekly
Get CVE alerts and security updates for io.github.anasmughal239-alt/domain-setup-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server for Claude and other MCP clients that sets up cold email domains in bulk on Cloudflare: verification TXT, SPF, DKIM, DMARC, MX, custom tracking domains and website forwarding. Works with Google Workspace, Microsoft 365 and Amazon SES, and with Smartlead and Instantly tracking.
Use it to audit email deliverability DNS, fix SPF records, add DMARC, and roll out sending domains for outbound campaigns without hand-editing DNS.
Agencies set up dozens of domains per client by hand. One wrong SPF edit (a second record, an overwrite, an 11th lookup) or one DKIM key pasted onto the wrong domain silently breaks deliverability. This server plans every change as a reviewable diff, refuses unsafe plans, applies each domain atomically, and can undo any run.
| Tool | Writes? | What it does |
|---|---|---|
domain_audit | No | Checks SPF, DKIM, DMARC and MX on public DNS. No token needed. |
domain_plan | No | Builds a per-domain diff against current Cloudflare records. Returns a plan_id. |
domain_apply | Yes | Applies a plan, one atomic batch per domain. Dry run unless confirm=true. Returns a run_id. |
domain_verify | No | Confirms every planned record is visible on public DNS and that forwarding answers with its 301. |
domain_rollback | Yes | Undoes one apply run, including redirect rules. Dry run unless confirm=true. |
All tools take lists of domains (max 100 per call). One failing domain never stops the batch.
| Item | Google Workspace | Microsoft 365 | Amazon SES |
|---|---|---|---|
| Verification TXT | google-site-verification=... (per domain) | MS=ms... (per domain) | n/a |
| SPF | merge include:_spf.google.com | merge include:spf.protection.outlook.com | on MAIL FROM subdomain |
| MX | smtp.google.com (1) | value you supply (never guessed) | MAIL FROM: exactly one MX |
| DKIM | TXT you supply (per domain) | 2 CNAMEs you supply (per domain) | 3 CNAMEs from tokens |
| Extra | autodiscover CNAME | ||
| DMARC | p=none default, quarantine optional, RFC 9989 np optional | same | same |
| Tracking | Smartlead emailtracking or Instantly inst | same | same |
| Forwarding | 301 from root and www to your site | same | same |
*.mx.microsoft for new domains in July 2026, and Microsoft says the admin center or Graph API is the only source of truth. Microsoft DKIM targets contain a routing character Microsoft assigns. The tool asks for both.replace_mx=true. Existing DMARC is never changed. Existing website records are never overwritten by forwarding.