Skip to main content
Glama
Sign In
Official Porkbun MCP Server

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Connect Domains To Cloudflare

connect_domains_to_cloudflare
DestructiveIdempotent

Queue domains to move into your Cloudflare account: Porkbun creates the zone, copies DNS records, and repoints registry nameservers in the background.

Instructions

Queue domains to move into the customer's own Cloudflare account: Porkbun creates the zone there, copies over the DNS records it holds, and repoints the registry nameservers at Cloudflare. ASYNCHRONOUS — a successful call means QUEUED, never connected; the work runs in the background over the next few minutes, so poll get_cloudflare_queue afterwards. Results are PER DOMAIN: each name comes back under queued, skipped or alreadyQueued with its own reason. A non-empty skipped is a NORMAL outcome (DNSSEC live, custom nameservers, already connected), NOT a failed call — report the reasons rather than calling the whole thing an error. Eligibility is re-checked right before each domain is acted on, so a queued domain can still be skipped later. Requires the Cloudflare account to be connected first (see get_cloudflare_connection). Use dry_run to preview verdicts without queueing. Max 500 domains per call.

Input Schema

NameRequiredDescriptionDefault
domainsYesDomain names to move into the customer's Cloudflare account.
dry_runNoPreview the per-domain verdicts without queueing anything.

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 destructiveHint=true and idempotentHint=true, and the description adds substantial context beyond that: it is asynchronous (success means QUEUED, not connected), eligibility is re-checked immediately before acting, and per-domain verdicts can still flip to skipped. It also discloses the 500-domain cap and the per-domain result buckets.

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 asynchronous warning and the per-domain result expectation before the operational detail. Dense but dense with substance; only the dry_run and 500-domain mentions mildly duplicate the schema.

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?

No output schema exists, and the description compensates by naming the three result buckets and their per-domain reasons, plus the polling follow-up. For a destructive, async, open-world mutation tool this is sufficient for correct invocation and result interpretation.

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 both parameters. The description restates the dry_run preview semantics already in the schema and confirms the 500 limit, but adds no syntax or format detail beyond that, so baseline 3 applies.

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 plus the full mechanism (creates zone, copies DNS records, repoints registry nameservers), which distinguishes it from siblings like preview_cloudflare_move and get_cloudflare_queue without opening any schema.

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?

Explicit when-to-use and what-to-do-elsewhere: poll get_cloudflare_queue afterwards, requires get_cloudflare_connection first, use dry_run to preview. It also warns that skipped verdicts are normal, which prevents a mis-selection of error-handling paths.

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