BunnyCDN MCP integration for AI agents.
Connect AI agents to BunnyCDN through 3 structured actions, including get pull zone, purge pull zone cache, and list pull zones. Review authentication, input…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the BunnyCDN integration exposes
The BunnyCDN Agent App exposes 3 provider-backed actions for storage and developer tools work. Its current contract lets an authorized agent get one bunny pull zone by id, purge the cache for a bunny pull zone, optionally restricted to one cache tag, and list bunny pull zones with optional pagination, search, and certificate expansion. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected BunnyCDN account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BunnyCDN capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_pull_zoneREADGet one Bunny Pull Zone by ID.
INPUTS: pullZoneId / includeCertificate
purge_pull_zone_cacheREVIEWPurge the cache for a Bunny Pull Zone, optionally restricted to one cache tag.
INPUTS: pullZoneId / cacheTag
list_pull_zonesREADList Bunny Pull Zones with optional pagination, search, and certificate expansion.
INPUTS: page / perPage / search / includeCertificate
INPUT CONTRACTS
Know what the action needs before it runs.
get_pull_zone
pullZoneIdREQUIRED- The Bunny Pull Zone ID.
includeCertificateOPTIONAL- Whether hostname certificate data should be included.
purge_pull_zone_cache
pullZoneIdREQUIRED- The Bunny Pull Zone ID.
cacheTagOPTIONAL- Optional cache tag used to purge only matching cached objects.
list_pull_zones
pageOPTIONAL- The page number to return.
perPageOPTIONAL- The page size to return when page is provided.
searchOPTIONAL- The search term used to filter pull zones by name or related text.
includeCertificateOPTIONAL- Whether hostname certificate data should be included.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Pull Zone
Get one Bunny Pull Zone by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_pull_zoneVerify with List Pull Zones
List Bunny Pull Zones with optional pagination, search, and certificate expansion. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_pull_zonesSAFETY BOUNDARY
Operate BunnyCDN with explicit limits
- Authorize BunnyCDN with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned BunnyCDN data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in BunnyCDN rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BunnyCDN task completed successfully.
CONNECTION MODEL
API key
Bunny account API key sent with the AccessKey header. Create or view it from the Bunny dashboard API Keys page: https://docs.bunny.net/account/api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by BunnyCDN.