Skip to main content
Glama
oborseth

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Hosting

create_hosting
Destructive

Provision static or WordPress hosting for a domain in a Porkbun account, starting a 15-day free trial that auto-renews at the plan price.

Instructions

Provision hosting for a domain in the account — Secure Static Hosting OR Cloud for WordPress (a managed WordPress site), chosen by sku. The domain's FIRST provision starts a 15-day FREE trial that auto-renews at the plan price ($3/mo or $30/yr) when it ends; a re-provision after deprovision is charged to account credit (one free trial per domain). Provisioning switches the domain to Porkbun nameservers if it isn't already — set agree_to_nameserver_change: true to allow that. You MUST echo the price in acknowledged_cost_cents (300 monthly / 3000 yearly) so the human is told about the auto-renew/charge. Use dry_run to preview. Provisioning can be async: status may be PENDING — poll get_hosting until ACTIVE before deploying. For a WordPress plan, the file tools (deploy_site/list_hosting_files/…) do NOT apply — manage the site through WordPress instead, using create_wp_credentials to get REST API credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuYesThe hosting plan SKU to provision. Discover the provisionable SKUs (and each one's price/interval/trial) via list_hosting_plans, then pass the row's `sku`. Secure Static Hosting: `PIXIESECURESTATICM2` ($3.00/mo) / `PIXIESECURESTATICY2` ($30.00/yr). Cloud for WordPress: `CLOUDWORDPRESSM1` ($12.00/mo) / `CLOUDWORDPRESSY1` ($120.00/yr) and the Pro/Business tiers.
domainYesDomain to provision hosting for, e.g. `example.com`.
dry_runNoValidate + preview without provisioning or charging.
agree_to_termsYesMust be "yes".
acknowledged_costNoDeprecated alias of `acknowledged_cost_cents`, same unit (integer US cents). Send `acknowledged_cost_cents` instead.
acknowledged_cost_centsNoThe chosen plan's price — take the `price` field of the SAME row you took `sku` from in list_hosting_plans (e.g. 300 static monthly, 3000 static yearly, 1200 WordPress Starter monthly, 12000 WordPress Starter yearly). Must match exactly or the call is rejected — this confirms the human was told the cost. Required. Integer US cents: 803 means $8.03, not $803.
agree_to_nameserver_changeNoSet true to allow switching the domain to Porkbun nameservers (required when it isn't already on them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.39.4

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare a destructive, non-readonly mutation, and the description adds substantial context beyond them: the 15-day free trial with auto-renew, re-provision charging, one-trial-per-domain limit, mandatory nameserver switch, the cost-acknowledgment gate, and async PENDING status. This is a genuinely informative behavioral profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then sequenced into trial/billing, nameserver, cost-ack, dry-run, async, and WordPress caveats. Dense but nearly every clause carries operational weight; slightly long for a single tool description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description covers the async lifecycle, the polling target, the SKU-dependent tooling difference, and the billing implications. An agent has everything needed to call this correctly and handle the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents sku, domain, dry_run, agree_to_terms, acknowledged_cost_cents, and agree_to_nameserver_change in detail. The description reinforces the cost-echo requirement and nameserver consent but adds little syntax or format detail beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (provision hosting for a domain) and explicitly scopes the two plan families (Secure Static Hosting vs Cloud for WordPress) selected by `sku`. It cleanly distinguishes itself from siblings like list_hosting_plans, get_hosting, and deploy_site.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use `dry_run` to preview, poll get_hosting until ACTIVE before deploying, and for WordPress plans use create_wp_credentials instead of the file tools. Both when-to-use and when-not-to-use are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools