7 operations. Call each with POST https://app.chirply.io/api/v1/actions/<name> and a bearer token; the response is { "data": { "action", "summary", "result" } }. A read badge means the operation changes nothing; write requires the credential’s write scope.
View WordPress hosting options
wordpress_sites.catalogreadadmin only
Lists live DigitalOcean regions, the WordPress plans with current monthly server prices, and every domain visible through its connected Cloudflare account.
Over MCP the same operation is the tool wordpress_sites_catalog at https://app.chirply.io/api/mcp, same bearer token, same input.
Check WordPress domain
wordpress_sites.check_domainreadadmin only
Checks whether a hostname belongs to its connected Cloudflare account and lists existing A, AAAA, or CNAME records that a WordPress launch would replace. Makes no DNS changes.
Parameters
Field
Type
Required
Description
domain
string
required
The complete root domain or subdomain to inspect, such as example.com or blog.example.com.
Over MCP the same operation is the tool wordpress_sites_check_domain at https://app.chirply.io/api/mcp, same bearer token, same input.
Destroy site
wordpress_sites.destroywriteconfirmadmin only
PERMANENTLY DELETES the WordPress Droplet and its managed DigitalOcean firewall, stopping future server and backup charges. The website, database, and files on that server cannot be recovered unless an independent snapshot exists.
Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.
Over MCP the same operation is the tool wordpress_sites_get at https://app.chirply.io/api/mcp, same bearer token, same input.
Launch WordPress site
wordpress_sites.launchwriteconfirmadmin only
CREATES BILLABLE INFRASTRUCTURE in its own DigitalOcean account. Creates a Droplet, paid backups when enabled, a cloud firewall, hardened WordPress, database, Redis, automatic updates, DNS records when authorized, and HTTPS. DigitalOcean bills the connected team until the site is destroyed.
Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.
Parameters
Field
Type
Required
Description
name
string
required
Site name shown here and used as the initial WordPress title.
domain
string
optional
Optional public domain, such as example.com. Omit to launch on the server IP first.
include_www
boolean
optional
Also route and secure www.<domain> when a domain is supplied. Default: true
region
string
required
Live DigitalOcean region slug returned by wordpress_sites.catalog, such as nyc3.
plan
"starter" | "business" | "pro"
required
WordPress plan mapped to a DigitalOcean server size.
Explicitly allow replacing existing A, AAAA, or CNAME records at the selected hostname. Required when wordpress_sites.check_domain reports a collision. Default: false
admin_email
string (email)
required
Email for the first WordPress administrator and Let's Encrypt expiry notices.
admin_user
string
required
Username for the first WordPress administrator.
admin_password
string
required
Password for the first WordPress administrator. It is encrypted only during bootstrap and then deleted from storage here.
Over MCP the same operation is the tool wordpress_sites_launch at https://app.chirply.io/api/mcp, same bearer token, same input.
List WordPress sites
wordpress_sites.listread
Lists this account's DigitalOcean WordPress sites, including server, DNS, HTTPS, provisioning, and cost status. Never returns passwords or OAuth tokens.
Over MCP the same operation is the tool wordpress_sites_list at https://app.chirply.io/api/mcp, same bearer token, same input.
Retry setup
wordpress_sites.retrywriteconfirmadmin only
Resume a stalled or failed WordPress launch. CAN CREATE BILLABLE INFRASTRUCTURE: if the launch never got as far as creating its server, this CREATES THE DIGITALOCEAN DROPLET (plus paid backups when the site was configured with them), which DigitalOcean bills the connected team for until the site is destroyed. Only when the site already has a server does it merely re-run the bootstrap, DNS and HTTPS checks, adding no new charge — and in that case it may still write the site's DNS records at the configured hostname. Check wordpress_sites.get first: a site with no server id is the billable case.
Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.