BunnyCDN

@bunnycdn list all my pull zones and show me which ones have caching enabled, sorted by monthly bandwidth usage

Based on your BunnyCDN account, you have 4 active pull zones. Here's the breakdown sorted by bandwidth: 1. **cdn.example.com** (enabled caching) - 2.4 TB last 30 days 2. **assets.myapp.io** (enabled caching) - 890 GB last 30 days 3. **static.demo.net** (caching disabled) - 340 GB last 30 days 4. **media.test.com** (enabled caching) - 120 GB last 30 days Note: This is an illustrative example showing typical pull zone data structure. Your actual zones and bandwidth metrics will vary based on your account configuration.

This read-heavy example demonstrates the MCP's ability to fetch and synthesize CDN configuration data. Requires a valid API key with read permissions for pull zones. BunnyCDN's API returns detailed metrics, but rate limits apply (300 requests/minute), so avoid polling this repeatedly in automated workflows.

@bunnycdn create a new storage zone called 'user-uploads' in the New York region with password protection enabled

Storage zone created successfully: **Name:** user-uploads **Region:** New York (US East) **Storage Zone ID:** 47823 **FTP Hostname:** ny.storage.bunnycdn.com **Password Protection:** Enabled Your storage zone is now active. You can upload files via FTP, HTTP API, or the BunnyCDN dashboard. The zone is currently empty (0 files, 0 GB used). Remember to configure CORS settings if you plan to access files from web applications. This example illustrates the typical response structure; actual zone IDs and hostnames will differ.

This write example shows the MCP creating infrastructure with side effects — a billable storage zone now exists in your account. The action is immediate and cannot be undone via the MCP (you'd need to explicitly delete it). Requires API key with storage zone write permissions. Consider cost implications before creating zones in production.

@bunnycdn check my DNS zones and draft a migration plan if I wanted to move my apex domain from Cloudflare to BunnyCDN DNS

You currently have 2 DNS zones configured in BunnyCDN: - **api.example.com** (4 records: 2 A, 1 CNAME, 1 TXT) - **cdn.myapp.io** (2 records: 1 A, 1 AAAA) **Migration Plan for Apex Domain:** 1. Create a new DNS zone in BunnyCDN for your apex domain 2. Replicate existing records (A, MX, TXT for email/verification) 3. Update nameservers at your registrar to BunnyCDN's NS records 4. Monitor propagation (24-48 hours) 5. Verify MX records resolve correctly before decommissioning Cloudflare zone **Risks:** Email delivery interruption if MX records misconfigured; SPF/DKIM records must transfer exactly. Test with a subdomain first. This is an illustrative analysis based on typical DNS zone structures.

This synthesis example pairs BunnyCDN's DNS data with AI reasoning to produce actionable migration guidance. The MCP provides the raw zone/record data; the AI interprets it contextually. Useful for infrastructure planning, but always verify DNS changes in staging before production. DNS propagation delays mean changes aren't instant.

When BunnyCDN beats manual CDN config for small marketing teams

A 3-person marketing team launching a product site needs CDN coverage in APAC and Europe but doesn't want to context-switch into Cloudflare's UI every deploy. The BunnyCDN MCP wins here because you can script pull zone creation and DNS record updates from the same chat where you're reviewing copy changes. The API key auth means one secret in the workspace, and the 20 tools cover the full lifecycle from zone creation to teardown. This breaks down if you need advanced edge logic or Workers-style compute—BunnyCDN is pure caching and storage, not a programmable edge. If your workflow is 'spin up a CDN endpoint, point DNS, forget it,' this MCP saves the tab-switching tax and keeps the deployment narrative in one thread.

Storage zone provisioning for per-client file delivery

A 6-person SaaS team delivers white-labeled PDFs and videos to enterprise customers, each needing isolated storage with regional compliance. The BunnyCDN MCP fits when you're provisioning storage zones per customer as part of onboarding automation. You can create the zone, configure replication, and hand off the endpoint URL without leaving the workspace where you're tracking the customer setup checklist. The toolset handles zone lifecycle cleanly, but it doesn't manage file uploads or access policies—you'll still need separate automation for that. This works if your bottleneck is the CDN infrastructure provisioning step, not the content pipeline itself. If you're provisioning more than 10 zones a week, the MCP keeps the ops overhead flat instead of growing with customer count.

DNS record updates during outage mitigation

A 4-person DevOps rotation handles incidents where origin servers fail and traffic needs immediate DNS failover to a backup pull zone. The BunnyCDN MCP is the right call when your runbook lives in Switchy and you need to update DNS records or swap pull zone origins mid-incident without opening the BunnyCDN dashboard. The get-details and delete-record tools let you verify state and roll back changes in the same chat thread as your incident log. This falls apart if you need sub-60-second DNS propagation or complex health-check logic—BunnyCDN's API is fast but not instant, and the MCP doesn't expose health monitoring. If your MTTR target allows 2-5 minute DNS changes and your team already uses Switchy for incident coordination, this MCP collapses the tool count during high-pressure moments.