Menu
Mattering Automations connector

A bunny.net MCP for workflows that reach past the CDN

Connect one account API key and pull zones, cache purge, edge rules, Bunny DNS, storage zone management, traffic statistics, and billing reads become workflow steps. An AI agent can repoint a DNS record with a zone export already in hand, a deploy webhook can purge exactly the paths that changed, and the results land next to your tasks and databases instead of in a terminal.

38 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the bunny.net MCP connector does

The bunny.net connector for Mattering Automations is 38 nodes on the bunny.net core API: CDN pull zones from creation through custom hostnames, Force SSL, and edge rules, cache purge by zone, by cache tag, or by URL with wildcards, Bunny DNS zones and records with BIND zone-file export, storage zone management from creation to replication settings, CDN, DNS, and storage statistics over any date window, billing reads, and Bunny Stream video library reads. One account API key, sent as bunny.net's AccessKey header, authenticates all of it.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can list a zone's DNS records, export the zone as a BIND file before anything changes, point a record at a new origin, and purge the cache for the paths that moved, without anyone opening the bunny.net dashboard.

bunny.net does not publish an official MCP server; the bunny.net MCP servers in the public directories are community built. bunny.net's own answer for AI agents is its CLI, a terminal tool built so that the commands a person runs are the same commands an automation or an agent runs, and for a developer whose agent already lives in a shell it is a genuine option. This connector is the other route: the same bunny.net operations exposed over MCP and on the Mattering canvas, where they sit next to every other connector and the platform itself. A deploy webhook can purge cache and then open a verification task, a DNS change can wait behind a human approval step, credentials live in one place with the rest of your connector secrets, and no agent needs shell access to do any of it.

The safety modeling is stated plainly. Of the 38 nodes, 18 read and 20 act, and five are flagged destructive: pull zone, storage zone, DNS zone, DNS record, and edge rule deletes. The storage zone delete deserves the extra sentence it gets on the node itself: it removes every file stored in the zone, unrecoverably, and by default also deletes pull zones linked to it. Scope is stated honestly too: this connector manages storage zones and video libraries, but bunny.net's file upload and video upload APIs are separate services on separate hosts with their own per-zone and per-library credentials, so file and video operations are deliberately not here. And because bunny.net's own API embeds storage passwords and Stream keys inside zone and library responses, the nodes that return them say so in their descriptions so you treat their output accordingly.

One connection, three surfaces

  • Visual automations. Drag bunny.net nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every bunny.net node, ready to drop on the canvas

38 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 18

bunny.net: Export DNS Zone

Export a DNS zone as a BIND zone file (plain text). Use it as a backup before destructive changes or to migrate records to another provider.

bunny.net: Get Billing Details

Current billing state of the account: balance, this month's charges broken down by product and traffic region, monthly bandwidth used, and recent billing records. A point-in-time gauge of the account, not a windowed report.

bunny.net: Get Billing Summary

Per pull zone usage summary for the current month: each zone's monthly usage amount and bandwidth used, as a plain array. A point-in-time gauge, not a windowed report.

bunny.net: Get Country List

List countries as bunny.net knows them: name, ISO code, EU membership, and tax metadata. The ISO codes are the values used in pull zone country block lists (BlockedCountries via Extra body fields on the update node).

bunny.net: Get DNS Query Statistics

DNS query statistics for a zone over a date window: total queries served for the whole window plus charts keyed by timestamp (QueriesServedChart, NormalQueriesServedChart, SmartQueriesServedChart) and a breakdown keyed by record type (QueriesByTypeChart). Defaults to the last 30 days when no window is set.

bunny.net: Get DNS Zone

Fetch one DNS zone with its full record list, nameserver configuration, SOA email, and DNSSEC status.

bunny.net: Get Pull Zone

Fetch one pull zone: origin, hostnames, cache and security settings, geo zones, and its edge rules (each with the Guid used by the edge rule nodes, at data.EdgeRules[].Guid).

bunny.net: Get Statistics

CDN traffic statistics over a date window, account-wide or filtered to one pull zone or region: whole-window totals (bandwidth, requests, cache hit rate, origin response time) plus charts keyed by timestamp (BandwidthUsedChart, RequestsServedChart, CacheHitRateChart, and more) and a geographic traffic breakdown. Defaults to the last 30 days when no window is set.

bunny.net: Get Storage Zone

Fetch one storage zone: name, main and replication regions, files stored, storage used, and its passwords for the separate storage file API (treat as sensitive).

bunny.net: Get Storage Zone Regions

List the available storage regions with their codes (used as the Region and replication values when creating a storage zone), names, and storage hostnames.

bunny.net: Get Storage Zone Statistics

Storage usage over a date window: bytes stored and file count as charts keyed by timestamp (StorageUsedChart, FileCountChart). Both series are point-in-time gauges of the zone's size, not per-day flows; never sum them across days. Defaults to the last 30 days when no window is set.

bunny.net: Get Video Library

Fetch one video library: player and encoding configuration, linked pull zone and storage zone, and its Stream API keys (treat as sensitive).

bunny.net: List DNS Zone Records

List a DNS zone's records as a paginated Items envelope: record IDs, integer type codes, names, values, and TTLs. The record ID from here feeds the update and delete nodes.

bunny.net: List DNS Zones

List the account's DNS zones as a paginated Items envelope: zone IDs, domains, nameserver status, and logging settings. The zone ID from here feeds every DNS node.

bunny.net: List Pull Zones

List the account's CDN pull zones with their numeric IDs, names, origin URLs, hostnames, and edge rules. By default (page blank) bunny.net returns every zone as a plain array; set page to 1 or higher for a paginated Items object. The pull zone ID from here feeds every pull zone node and the statistics filter.

bunny.net: List Storage Zones

List the account's storage zones with IDs, names, regions, usage, and connected pull zones. By default (page blank) bunny.net returns every zone as a plain array. The response includes each zone's storage passwords (that is how the separate storage file API authenticates), so treat the output as sensitive.

bunny.net: List Video Libraries

List the account's Bunny Stream video libraries: IDs, names, video counts, and storage usage. Returns a plain array by default; set page to 1 or higher for a paginated Items envelope instead. The response includes each library's Stream API keys by design of the vendor API, so treat the output as sensitive. Video upload and management happen on the separate Stream API host, out of scope for this connector.

bunny.net: Region List

List the bunny.net CDN regions with their numeric IDs (used by the statistics region filter), region codes, names, and coordinates.

Action nodes 20

bunny.net: Add DNS Record

Add a record to a DNS zone (a PUT request per the vendor spec). Returns the created record including its ID. Reversible with bunny.net: Delete DNS Record.

bunny.net: Add Pull Zone Hostname

Attach a custom hostname (for example cdn.example.com) to a pull zone. Point the hostname's DNS at the zone's b-cdn.net hostname with a CNAME, then issue SSL separately. Returns 204 with no body. Reversible with bunny.net: Remove Pull Zone Hostname.

bunny.net: Add or Update Edge Rule

Create an edge rule on a pull zone, or update an existing one when its Guid is supplied. An edge rule pairs an action (redirect, header change, cache override, block) with URL or header triggers. Returns 201 with no body; read the resulting rules (and their Guids) with bunny.net: Get Pull Zone at data.EdgeRules[].

bunny.net: Create DNS Zone

Add a domain to Bunny DNS. The zone is served by the bunny.net nameservers once the domain's registrar points at them. The vendor spec documents the 201 response without a body, so follow with List DNS Zones to read the new zone's ID. Reversible with bunny.net: Delete DNS Zone.

bunny.net: Create Pull Zone

Create a CDN pull zone from a URL origin or a bunny.net storage zone. Name becomes the default hostname name.b-cdn.net. The vendor spec documents the 201 response without a body, so follow with List Pull Zones or Get Pull Zone to read the new zone's ID. Reversible with bunny.net: Delete Pull Zone. The full 146-field creation model (cache, security, Optimizer, logging) is reachable via Extra body fields.

bunny.net: Create Storage Zone

Create an edge storage zone. Returns the created zone including its ID and the passwords used by the separate storage file API. Replication regions cannot be removed later, only added. Reversible with bunny.net: Delete Storage Zone.

bunny.net: Delete DNS Record

DESTRUCTIVE: delete a DNS record. Whatever the record pointed at stops resolving; the record must be re-created to restore it (disable it instead if it might come back). Returns 204 with no body.

bunny.net: Delete DNS Zone

DESTRUCTIVE: delete a DNS zone and every record in it. The domain stops resolving through Bunny DNS immediately and the records cannot be restored; export the zone first with bunny.net: Export DNS Zone if there is any doubt. Returns 204 with no body.

bunny.net: Delete Edge Rule

DESTRUCTIVE: delete an edge rule from a pull zone. The rule's triggers and action configuration are removed and must be re-authored to restore; disable the rule instead if it might come back. Returns 204 with no body.

bunny.net: Delete Pull Zone

DESTRUCTIVE: delete a pull zone. Its hostnames, edge rules, and configuration are removed and content stops being served through the zone immediately; the configuration cannot be restored. Returns 204 with no body.

bunny.net: Delete Storage Zone

DESTRUCTIVE: delete a storage zone AND every file stored in it, unrecoverably. By default bunny.net also deletes pull zones linked to the storage zone. Returns 204 with no body.

bunny.net: Purge Pull Zone Cache

Purge a pull zone's entire cache, or only objects carrying a specific cache tag when CacheTag is set. Content is re-fetched from the origin on the next request; nothing is deleted at the origin, so this is safe but does raise origin traffic until the cache refills. Returns 204 with no body.

bunny.net: Purge URL

Purge a single URL from the CDN cache without knowing which pull zone serves it. Wildcards purge path families, for example https://example.b-cdn.net/assets/*. The next request re-fetches from the origin; nothing is deleted at the origin. Returns 200 with no body.

bunny.net: Remove Pull Zone Hostname

Detach a custom hostname from a pull zone (a DELETE request that carries a JSON body). The hostname stops serving through the zone; re-adding it reverses the change. Returns 204 with no body.

bunny.net: Set Edge Rule Enabled

Enable or disable one edge rule without editing it. Returns 204 with no body. Reversible by setting the opposite value.

bunny.net: Set Force SSL

Turn Force SSL on or off for one hostname on a pull zone (redirects HTTP requests to HTTPS when on). Returns 204 with no body. Reversible by setting the opposite value.

bunny.net: Update DNS Record

Update a DNS record. The vendor's update model carries the same fields as record creation, so send the record's intended state (read it first from bunny.net: List DNS Zone Records) rather than a single changed field. Returns 204 with no body.

bunny.net: Update DNS Zone

Update a DNS zone's settings: custom nameservers, SOA email, and query logging. Only fields you fill are sent. Returns the updated zone. Reversible by writing the previous values back.

bunny.net: Update Pull Zone

Update a pull zone's configuration (bunny.net updates use POST, not PATCH). Only fields you fill are sent; the rest of the 145-field settings model (geo zones, security, Optimizer, rate limits) is reachable via Extra body fields. Returns the updated zone. Reversible by writing the previous values back; read them first with bunny.net: Get Pull Zone.

bunny.net: Update Storage Zone

Update a storage zone's settings: add replication zones, set a fallback origin URL, a custom 404 file path, or rewrite 404s to 200. Only fields you fill are sent. Returns 204 with no body.

Connecting bunny.net takes one credential

bunny.net authenticates core API requests with the account API key, sent as an AccessKey header on every request. The key lives in the bunny.net dashboard at dash.bunny.net under Account, then API Key, where it can be revealed, copied, and regenerated. Every account has one, including trial accounts, and it carries full access to the account, so treat it like a root credential. It is a different credential from storage zone passwords and Bunny Stream library keys, which authenticate bunny.net's separate file and video APIs and are not what this connector stores.

1

Sign in at dash.bunny.net, open Account, then API Key. Use the eye icon to reveal the key and the copy icon to copy it.

2

In Mattering Automations, open Connectors, click Add Connector, choose bunny.net, and create a credential with the API key.

3

Click Test Connection. Mattering calls bunny.net's pull zone list endpoint, which every account key can read: a zone list, even an empty one, proves the credential, and a 401 means the key is wrong or has been regenerated.

4

All 38 bunny.net nodes appear in the canvas palette. Run bunny.net: List Pull Zones first for pull zone IDs and bunny.net: List DNS Zones for the zone IDs that every DNS node needs.

Common uses for the bunny.net MCP

Deploys that purge exactly what changed

A deploy webhook fires and the cache clears with the right blast radius. bunny.net: Purge Pull Zone Cache flushes a whole zone, or only the objects carrying a cache tag when CacheTag is set, and bunny.net: Purge URL clears a single URL or a wildcard path family like https://example.b-cdn.net/assets/* without even knowing which zone serves it. Nothing is deleted at the origin either way; the honest cost is that purged content is re-fetched from the origin on the next request, so tag and wildcard purges keep a release from turning into a full cold-cache hit.

An AI agent that manages DNS with an export habit

bunny.net: List DNS Zones and bunny.net: List DNS Zone Records show an agent what exists, bunny.net: Export DNS Zone captures the whole zone as a BIND file before anything changes, and then bunny.net: Add DNS Record and bunny.net: Update DNS Record do the work, with a destructive-flagged bunny.net: Delete DNS Record behind whatever gate you choose. One vendor quirk the nodes state up front: bunny.net's record update sends the record's full intended state, not a single changed field, so the read-first habit is not optional politeness, it is how the update is built.

Provision a CDN front end from a workflow

bunny.net: Create Pull Zone stands up a zone from a URL origin or a bunny.net storage zone, with the name becoming the default hostname at name.b-cdn.net. bunny.net: Add Pull Zone Hostname attaches the real domain, and bunny.net: Set Force SSL turns on the HTTP to HTTPS redirect per hostname. The full 146-field zone model, cache rules, security, Optimizer, logging, is reachable through the create and update nodes' Extra body fields, so the workflow that provisions a staging CDN for every preview branch does not stop at the defaults.

Edge rules as operational switches

An edge rule pairs an action, redirect, header change, cache override, or block, with URL or header triggers, and bunny.net: Add or Update Edge Rule writes them from a workflow. The quietly useful one is bunny.net: Set Edge Rule Enabled: it flips a rule on or off without editing it, which turns a prepared block rule or maintenance redirect into a switch an automation or an agent can throw and later throw back. Rule Guids live in the zone detail from bunny.net: Get Pull Zone, and the delete is flagged destructive because a removed rule must be re-authored.

Traffic and billing reporting that lands in a database

bunny.net: Get Statistics returns a date-windowed picture of CDN traffic, bandwidth, requests, cache hit rate, origin response time, with charts keyed by timestamp and a geographic breakdown, account-wide or filtered to one pull zone or region. bunny.net: Get DNS Query Statistics does the same for a DNS zone, and bunny.net: Get Billing Summary and bunny.net: Get Billing Details read the account's current balance and this month's per-zone usage. A scheduled sweep can write all of it into a Mattering database and open a task when bandwidth or the cache hit rate drifts.

Storage zones managed, files left where they belong

bunny.net: Create Storage Zone provisions edge storage with a main region and replication regions, bunny.net: Update Storage Zone adds replication later (bunny.net never removes replication regions, only adds them) and sets fallback origin and 404 behavior, and bunny.net: Get Storage Zone Statistics tracks bytes stored and file counts over time. The honest boundary: uploading, listing, and deleting the files themselves happens on bunny.net's separate storage API with per-zone passwords, which this connector deliberately does not hold. Manage the zones here; move the files with the tool that holds those keys.

Example: A release goes live: back up the zone, repoint the record, purge what changed

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: an inbound webhook from your CI pipeline fires when the deploy finishes, carrying the new origin address and the path prefix that changed.

2

bunny.net: Export DNS Zone captures the zone's full record set as a BIND file into the run, the backup that makes the rest of the workflow reversible.

3

bunny.net: List DNS Zone Records reads the record's current state, because bunny.net record updates send the record's full intended state rather than one changed field.

4

bunny.net: Update DNS Record points the record at the new origin.

5

bunny.net: Purge URL clears the changed paths with a wildcard, so the origin serves fresh content without absorbing a full cold-cache refill.

6

The workflow opens a verification task in Mattering Productivity with the exported zone file attached, so a person confirms the site is healthy and has the rollback in hand if it is not.

bunny.net MCP questions, answered

What bunny.net operations are supported?

38 nodes on the bunny.net core API: 18 query nodes and 20 action nodes covering pull zones (list, get, create, update, delete, custom hostnames, Force SSL, cache purge, and edge rules), purge by URL with wildcards, Bunny DNS (zones and records with full CRUD, BIND zone-file export, and query statistics), storage zone management (create, update, delete, regions, and storage statistics), CDN traffic statistics, billing details and per-zone billing summaries, region and country reference lists, and Bunny Stream video library reads. Deliberately not included: file operations inside storage zones, video upload and management, and bunny.net's separate product APIs such as Shield and Edge Scripting.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Is there an official bunny.net MCP server?

No, not as of this writing. The bunny.net MCP servers listed in public MCP directories are community built and not maintained by bunny.net. bunny.net's own tooling for AI agents is its CLI, a terminal tool designed so agents run the same commands people do, which works well when your agent already has shell access and you are comfortable handing it a terminal. This connector takes the other route: bunny.net operations over MCP and on a visual canvas, running on Mattering's infrastructure rather than a shell, with credentials stored once, destructive operations flagged, and the same nodes shared by automations and agents.

Can it upload files to a storage zone or videos to Bunny Stream?

No, and the boundary is bunny.net's own architecture rather than a missing feature. File operations use bunny.net's storage API on separate per-region hosts, authenticated with per-zone passwords, and video upload and management use the Stream API on its own host with per-library keys. Neither credential is the account API key this connector stores. The connector manages the zones and libraries themselves: create and configure storage zones, read storage statistics, and list video libraries. One consequence worth knowing: bunny.net's API includes those per-zone passwords and Stream keys inside storage zone and video library responses, so the nodes that return them warn about it in their descriptions.

Do I need a paid bunny.net account?

You need an account with an active trial or a positive balance. bunny.net gives new accounts a 14 day trial with trial credits, and after the trial it runs prepaid, pay as you go from a balance you top up; there is no permanent free tier. The API itself costs nothing extra: the account API key is available on every account, including during the trial, so you can build and test workflows against trial resources before committing a balance.

What are bunny.net's API rate limits?

bunny.net does not publish a request rate limit for its core API, so this page will not invent one. What bunny.net does publish are per-product service limits, separate documented limits pages for the CDN, DNS, and storage products covering things like pull zone and edge rule counts, DNS record counts, and storage request rates. If a heavy sweep does get refused, the nodes report the error on their output rather than silently retrying, so a workflow can wait and continue.

Can an AI agent safely manage DNS records?

That is one of the connector's designed-for jobs, and the guardrails are concrete. bunny.net: Export DNS Zone gives the agent a one-node BIND backup of the whole zone before anything changes, the delete nodes for records and zones are flagged destructive so workflows gate them behind conditions or approval steps, and the record update's read-first pattern is stated on the node itself. The honest pattern is list, export, then write, with deletes behind an approval task rather than a bare trigger.

What happens if an automation deletes a storage zone?

Everything goes. bunny.net: Delete Storage Zone removes the zone and every file stored in it, unrecoverably, and by default bunny.net also deletes the pull zones linked to that storage zone, so a single call can take down both the storage and the CDN endpoints serving it. The node is flagged destructive and its description says exactly this. Treat it accordingly: keep it out of automated paths entirely, or put it behind a human approval step, and never point it at a zone whose files exist nowhere else.

38 nodes waiting on the canvas

Put bunny.net to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. bunny.net is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products