Porkbun DNS š·
Let your coding agent list and update Porkbun DNS, domains, DNSSEC, and SSL from Claude Code or Cursor instead of the registrar UI.
Overview
Porkbun DNS MCP is a Cloud & Infrastructure MCP server for the Operate phase that lets agents manage Porkbun DNS records, domains, DNSSEC, and SSL over stdio.
What is this MCP server?
- Stdio MCP package porkbun-mcp 1.1.2 on PyPI with PORKBUN_API_KEY and PORKBUN_SECRET_KEY
- Read-only by default; set PORKBUN_GET_MUDDY=true to allow write operations
- Covers DNS records, domain management, DNSSEC, and SSL certificate workflows
- Fits launch cutovers and day-two infra changes on indie side projects
- GitHub source at major/porkbun-mcp for self-hosted stdio transport
- Server version 1.1.2
- Stdio transport via registry package identifier porkbun-mcp on PyPI
- Three documented environment variables including optional boolean PORKBUN_GET_MUDDY for writes
Community signal: 14 GitHub stars.
What problem does it solve?
Switching between your agent and Porkbunās web UI slows down DNS cutovers and makes it easy to mistype records when you ship or fix production domains.
Who is it for?
Indie builders who host on Porkbun and want MCP-driven DNS and SSL tasks during launch and ongoing infra tweaks.
Skip if: Teams on Cloudflare-only DNS, bulk registrar migrations, or anyone who cannot store Porkbun API secrets in a local agent environment.
What do I get? / Deliverables
After you register the server with your Porkbun keys, your agent can query and (when enabled) update DNS and certificate-related settings in conversational workflows.
- Agent-callable DNS, domain, DNSSEC, and SSL operations against your Porkbun account
- Safer read-only exploration until write mode is explicitly enabled
- Repeatable infra changes documented in chat instead of ad hoc UI clicks
Recommended MCP Servers
Journey fit
DNS, SSL, and domain records are ongoing production infrastructure; canonical shelf is operate/infra where solo builders keep domains healthy after ship. Porkbun MCP directly manipulates DNS records, DNSSEC, and certificatesāthe core infra surface for any custom domain product.
How it compares
Registrar-focused MCP integration, not a generic DNS skill or hosting provisioner.
Common Questions / FAQ
Who is Porkbun DNS MCP for?
Solo and indie developers who use Porkbun for domains and want Claude Code, Cursor, or similar agents to manage DNS and SSL via MCP instead of manual dashboard edits.
When should I use Porkbun DNS MCP?
Use it when you are pointing a new app to production, adding verification TXT records, adjusting DNSSEC, or maintaining certificatesāand you want read-only checks first, then writes with PORKBUN_GET_MUDDY enabled.
How do I add Porkbun DNS MCP to my agent?
Install porkbun-mcp from PyPI, set PORKBUN_API_KEY and PORKBUN_SECRET_KEY, optionally PORKBUN_GET_MUDDY for writes, and add the stdio server entry (io.github.major/porkbun) in your clientās MCP configuration.