Official Porkbun MCP Server

Share Site Access

share_site_access

Create an approval link so another person and their AI agent can run one domain's website without account access; the owner approves it on Porkbun, then shares a site-only link or QR code.

Instructions

Ask to let someone else, and the AI agent they use, run ONE domain's website (Cloud for WordPress, static hosting or Link in Bio) without giving them the account. Nothing is shared by this call: it returns an approveUrl that the account holder must open on porkbun.com and approve. Give them that link and say so plainly. After they approve, that page shows a share link and QR code to send to the other person (it opens a page with a handoff prompt for their AI assistant), and list_site_shares returns the link for this share. What the other person gets: the site permission on that domain only. They can run the site (WordPress via create_wp_credentials, files, Link in Bio, backups and restores, staging, PHP/WordPress versions, SSL), but cannot buy, cancel the hosting, change DNS, or see the rest of the account. The link works once, within claim_hours of approval; with access_hours the access then ends on its own that long after they connect (otherwise it lasts until revoked). The account holder is emailed when it is claimed and can end it with revoke_site_share or by deleting the key at https://porkbun.com/account/api.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>",
      "shared_with": "<shared_with>"
    },
    "name": "share_site_access"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	The domain whose website to share, e.g. `example.com`. It must have hosting or a Link in Bio page.
`dry_run`	No	Check the domain can be shared without creating anything.
`claim_hours`	No	How long the link works once approved, 1-168 hours (default 24).
`shared_with`	Yes	Who it is for, e.g. `Sarah`. Shown to the account holder when approving and to the other person on the share page.
`access_hours`	No	How long the access itself lasts once they connect, in hours (e.g. 48 for two days). Leave out for access until it is revoked. Ask the user if they mention a time limit.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.62.0Nov 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only say non-read-only, non-idempotent, non-destructive; the description adds the crucial behavior that nothing is shared by the call itself and an approveUrl must be opened by the account holder. It further discloses the one-time link, claim_hours and access_hours lifetimes, the email notification on claim, and the two revocation paths, all of which an agent needs to set expectations correctly.

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?

The most important fact, that no sharing happens until approval, is front-loaded in sentence two, and the flow reads in execution order. It is dense and runs long, with a parenthetical capability list (files, backups, staging, PHP/WordPress versions, SSL) that could be trimmed without losing meaning.

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?

With no output schema, the description carries the return-value burden and does so: it explains the approveUrl response, the approval page, the resulting share link and QR code, and where list_site_shares surfaces it. For a multi-step, non-idempotent sharing tool this is complete enough to invoke correctly on the first try.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the prose adds the interaction between the two timers (link works once within claim_hours of approval, then access ends access_hours after connecting) and stresses 'ask the user if they mention a time limit'. dry_run and shared_with are left to the schema, which already documents them well.

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 (share one domain's website access) and immediately scopes it: ONE domain, Cloud for WordPress / static hosting / Link in Bio, without giving away the account. It also names complementary siblings (list_site_shares, revoke_site_share, create_wp_credentials), so an agent can place it in the toolset without opening the schema.

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

Usage Guidelines4/5

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

The opening sentence defines the triggering situation (someone else, plus their AI agent, needs to run a site without account access), and the description routes to list_site_shares for retrieval and revoke_site_share for termination. It stops short of explicit when-not-to-use guidance, e.g. whether this should be preferred over creating a separate API key or a WP credential.

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

Deploy Server