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 tools have overlapping or indistinguishable purposes, especially dns_delete vs dns_remove vs dns_delete_by_name_type, dns_edit vs dns_edit_by_name_type, and dns_get vs dns_get_by_name_type. Setup/orchestration tools like dns_setup, subdomain_setup, email_dns_setup, domain_cutover_web, and update_server_ip are hard to distinguish without descriptions, and most tools lack descriptions entirely.
Most names use snake_case, which is readable, but conventions vary: some groups use plural resource prefixes (domains_list) while others use singular or bare verbs (dns_list, ssl_retrieve, ping). Verb choices are inconsistent across equivalent operations, such as delete vs remove and edit vs update, and several tools have no resource prefix at all.
At 40 tools, the surface is heavy for a Porkbun management server, and much of the count comes from near-duplicate variants like dns_delete and dns_delete_by_name_type. The broad domain/DNS feature set could justify many tools, but the current set appears bloated by redundant operations.
The tool surface covers a wide range of domain management workflows: domains, DNS records, DNSSEC, SSL retrieval, nameservers, URL forwarding, glue records, availability checks, pricing, and health/setup helpers. Minor gaps may exist around account-level or transfer operations, but the core lifecycle appears well covered.