Porkbun

Porkbun MCP server

Run your Porkbun account from your AI assistant: find and register domains, edit DNS and DNSSEC, publish a static site, transfer a domain in or move its DNS to Cloudflare, set up mailboxes and webhooks, and read invoices. The tools are Porkbun's own (@porkbunllc/mcp-server), plus a zone file export, with safety around them. Every tool that spends money, commits to a charge, changes a domain's owner or hands out a secret is money: your client asks you first, and a charge over the account's monthly API limit is refused before it reaches Porkbun.

You need a Porkbun account and an API key pair (pk1_... and sk1_...), each half in a file, with API access turned on for the domains it should manage. Purchases are paid from account credit, or by your card through Stripe Link. To save a file (a certificate, an invoice PDF, a zone file, a mailbox password), the server also needs a directory to save into.

What you can ask

• "Which of my domains expire in the next three months, and which of those have auto-renew off?"
• "Is talonbakery.com available? If it costs less than $15 a year, register it."
• "Back up the DNS of example.com, then point shop.example.com at 203.0.113.10."
• "Publish the site in ./dist to example.com's static hosting."
• "If I moved example.org to my Cloudflare account, which DNS records would be dropped?"
• "Save last month's Porkbun invoice as a PDF."

Install

.%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22porkbun_secret_api_key_file%22%2C%22description%22%3A%22Path%20of%20a%20file%20holding%20your%20Porkbun%20secret%20API%20key%20(sk1_...).%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22porkbun_outbox_dir%22%2C%22description%22%3A%22Optional.%20Where%20the%20tools%20that%20save%20a%20file%20(an%20SSL%20bundle%2C%20an%20invoice%20PDF%2C%20a%20DNS%20zone%20export%2C%20a%20new%20mailbox's%20password)%20write%20it.%20Without%20it%20those%20tools%20answer%20with%20a%20configuration%20error%3B%20every%20other%20tool%20works.%22%7D%2C%7B%22type%22%3A%22promptString%22%2C%22id%22%3A%22porkbun_toolsets%22%2C%22description%22%3A%22Optional.%20The%20toolsets%20whose%20tools%20the%20server%20loads%2C%20separated%20by%20commas%2C%20e.g.%20dns%2Cforwards.%20Empty%20loads%20every%20toolset.%22%7D%5D&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40foreverworks%2Fmcp-porkbun%22%5D%2C%22env%22%3A%7B%22PORKBUN_API_KEY_FILE%22%3A%22%24%7Binput%3Aporkbun_api_key_file%7D%22%2C%22PORKBUN_SECRET_API_KEY_FILE%22%3A%22%24%7Binput%3Aporkbun_secret_api_key_file%7D%22%2C%22PORKBUN_OUTBOX_DIR%22%3A%22%24%7Binput%3Aporkbun_outbox_dir%7D%22%2C%22PORKBUN_TOOLSETS%22%3A%22%24%7Binput%3Aporkbun_toolsets%7D%22%7D%7D)

With Claude Code:

claude mcp add porkbun -e PORKBUN_API_KEY_FILE="<path to API key file>" -e PORKBUN_SECRET_API_KEY_FILE="<path to Secret API key file>" -- npx -y @foreverworks/mcp-porkbun

Claude Desktop (Settings, Developer, Edit Config) and most other clients read the same command as JSON:

{

"mcpServers": { "porkbun": { "command": "npx", "args": ["-y", "@foreverworks/mcp-porkbun"], "env": { "PORKBUN_API_KEY_FILE": " ", "PORKBUN_SECRET_API_KEY_FILE": " " } } } }

Each runs the published package on Node 22.19 or newer. VS Code and the Claude Desktop bundle ask for each setting as they add the server; leave an optional one empty. Cursor reads each from your environment instead (${env:PORKBUN_API_KEY_FILE} and so on), so set them before you start Cursor. The commands above set only what is required; Configuration has the rest.

From a clone

git clone https://github.com/foreverworks/mcps.git && cd mcps

npm ci && npm run build claude mcp add porkbun -e PORKBUN_API_KEY_FILE=" " -e PORKBUN_SECRET_API_KEY_FILE=" " -- node "$PWD/servers/porkbun/dist/index.js"

In a JSON configuration, the command is node and its one argument the full path of servers/porkbun/dist/index.js. To share one running copy between several clients over HTTP, see docs/deploying.md.

Configuration

The keys are read on the first call that needs them, so the documentation tools (read_doc, search_docs, list_doc_topics), get_pricing and mock_call work without them. The keys are never logged or returned: the audit line carries no arguments or results.

A deployment that limits egress sets MCP_EGRESS_ALLOW=api.porkbun.com,porkbun.com. deploy_site and import_dns_records read files from MCP_FILE_ROOTS. Both, and the other variables every server shares, are in docs/configuration.md.

Getting the API key pair

1. Sign in at porkbun.com and open API Access.
2. Create a key for this server alone, so you can restrict and revoke it on its own. Porkbun shows the secret key once: copy both halves now.
3. Optionally restrict the key (there, or later with the gear icon next to it): Allowed IPs, Allowed domains, and Permissions (Full access, Read-only, Manage, but no purchases, or custom scopes). A call outside them fails and changes nothing.
4. Save each half in a file readable only by you (chmod 600), and point PORKBUN_API_KEY_FILE and PORKBUN_SECRET_API_KEY_FILE at them.
5. Turn on API access for the domains: Opt In All Domains on the same page, or each domain's API Access under Domain Management. Without it, every call on that domain fails.

Toolsets

Every tool definition the server hands your client travels with each request the client makes, and Porkbun's are long. PORKBUN_TOOLSETS names the toolsets to load, separated by commas. The tools of the others are not there at all, and the server's instructions tell the assistant which toolsets are missing, so it can tell you instead of looking for a way around. Unset, empty or all, every toolset is loaded, as before.

ping, get_balance and get_api_settings are always loaded: ping is where you start and where a failure is diagnosed, and every purchase, in five of the toolsets, is paid from the balance and counts against the monthly API spend cap. Whatever is loaded, a purchase is still money and still checked against the caps before it is sent. A name that is not a toolset stops the server at start, with a message listing the ones there are. src/mcp/toolsets.ts places each tool by name, and a version of Porkbun's package with a tool it does not place fails the tests and will not start. Measured with scripts/measure-tokens.ts on 2026-10-23 (GPT-4 tokenizer), the tool list is 113 tools and about 44,200 tokens with every toolset, 23 tools and 8,800 with dns,forwards, and 25 tools and 12,300 with domains,account.

To load DNS and forwarding only:

{

"mcpServers": { "porkbun": { "command": "npx", "args": ["-y", "@foreverworks/mcp-porkbun"], "env": { "PORKBUN_TOOLSETS": "dns,forwards", "PORKBUN_API_KEY_FILE": "/path/to/porkbun-api-key", "PORKBUN_SECRET_API_KEY_FILE": "/path/to/porkbun-secret-api-key" } } } }

A toolset removes tools; MCP_MAX_ACCESS=read keeps every tool listed and refuses the writes.

First run

1. Ask your assistant to run Porkbun's ping. It checks the connection and the key pair, and shows the key's scopes.
2. Ask for the API spend settings (get_api_settings) and the balance (get_balance): what the account may still spend this month, and the credit a purchase is paid from.
3. Purchases and top-ups need a verified email and phone. If a call answers VERIFICATION_REQUIRED, the assistant sends each code (send_email_verification_code, send_phone_verification_code) and you read it back to confirm.

Tools

read changes nothing; write changes the account, its DN