porkbun-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORKBUN_API_KEY | Yes | Your Porkbun API key | |
| PORKBUN_GET_MUDDY | No | Set to true to enable write mode | false |
| PORKBUN_SECRET_KEY | Yes | Your Porkbun secret API key | |
| PORKBUN_ENABLE_DOMAIN_CREATE | No | Set to true to enable domain creation (dangerous) | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 40 tools
Many DNS tools overlap (dns_list, dns_get, dns_query; dns_edit, dns_upsert, dns_batch_apply) and high-level tools like dns_setup, subdomain_setup, and domain_cutover_web duplicate lower-level functions. Without descriptions, agents cannot reliably distinguish them.
Most tools use a noun_verb pattern (e.g., domains_list, dns_create), but several are verb-first (update_server_ip, dns_upsert) or use awkward noun phrases (domain_health_check, dns_audit). Resource prefixes are inconsistent: domains_, dns_, domain_ (singular), ssl_, and no prefix.
40 tools is excessive for the apparent scope, especially with several overlapping operations (e.g., three DNS retrieve functions, four DNS modify functions). Many could be consolidated without losing capability.
The set covers core domain and DNS CRUD, DNSSEC, URL forwards, glue records, and SSL retrieval. However, domain deletion, transfer, and SSL provisioning are absent, and high-level automation tools (dns_setup, subdomain_setup) may not fill these gaps.