# bunny-mcp
MCP server for [Bunny.net](https://digitizer.li/bunny) — pull zones, DNS, storage, video streaming, edge scripting, Shield/WAF and Magic Containers, from an AI assistant.
A hardened fork of [anvme/bunnycdn-mcp](https://github.com/anvme/bunnycdn-mcp) (MIT). Two things differ, and both exist because pointing the upstream at a real Bunny account publishes credentials.
## Part of the Aura Design Engine
These are the skills behind [**Aura**](https://my-aura.app) — one AI web-agency lifecycle you can run standalone or orchestrate across a whole client fleet from a single dashboard.
| Stage | Skill | Role |
| --- | --- | --- |
| 🎨 Build | [siteagent-elementor-studio](https://github.com/Digitizers/siteagent-elementor-studio) · [elementor-mcp](https://github.com/Digitizers/elementor-mcp) | Design & build sites inside Elementor — the recipes, and the MCP engine under them |
| 🔎 Audit + Content | [wordpress-api-pro](https://github.com/Digitizers/wordpress-api-pro) | REST content ops, SEO & site audits |
| 🖥 Host | [cloudways-mcp](https://github.com/Digitizers/cloudways-mcp) · [hostinger-mcp](https://github.com/Digitizers/hostinger-mcp) | Provision & operate the infrastructure |
| 🚀 Deliver | [**bunny-mcp** ← you are here](https://github.com/Digitizers/bunny-mcp) | CDN, storage & edge delivery |
| 🛡 Govern | [aura-mcp](https://github.com/Digitizers/aura-mcp) | Drive the control plane — approvals, snapshots, rollbacks — over MCP |
**→ Orchestrate all of it across your client fleet with [Aura](https://my-aura.app)** — governed agent ops with approvals and a full audit trail on top of these skills.
## What the fork changes
### 1. Responses are projected through an allow-list
Bunny returns credentials inline with ordinary metadata:
| Endpoint | Credential in the response |
|---|---|
| `GET /pullzone` | `ZoneSecurityKey` — the token-authentication signing secret, for every zone |
| `GET /pullzone` → `Hostnames[]` | `Certificate` and `CertificateKey` — the TLS private key |
| `GET /storagezone` | `Password`, `ReadOnlyPassword` — full read-write and read storage keys |
| `GET /videolibrary` | `ApiKey`, `ReadOnlyApiKey`, `WebhookSignatureKey` |
| `GET /user` | `ApiKey` — the account key the server itself authenticates with |
Handing those to a model puts them in its context, its logs and its transcript. So no tool ever sees them: every response passes through [`lib/project.js`](lib/project.js) at the HTTP layer, keyed by request path, and only the fields named there survive.
It is an **allow-list, not a deny-list**. Stripping known secret names fails the moment Bunny adds a field — the new one ships in the clear and nothing tells you. Naming what may pass fails the other way: a new field is invisible until someone decides it is safe.
It **fails closed**. A path with no declared shape returns no data and an error naming the path, rather than the raw payload.
It applies **inside a value, not only to it.** A URL keeps scheme, host, port and path; userinfo, query and fragment go. The first version of that scrubber removed `user:password@` and kept the rest — a deny-list wearing a scrubber's coat, which closed the one place a credential was known to sit and let `?token=…` walk through. And a free-form bag is a bag whether it arrives as an object or a string: `CustomHTML` is dropped for the same reason `metaTags` is.
It **does not vet structure by naming its parent.** A bare field name may only carry a scalar, or an array of them; an object survives only where a nested shape is declared for it. Every leak found while reviewing this fork lived one level below a name someone had already vetted — `Hostnames` looked safe and held the TLS private key; `EdgeRules` was given a shape and `ExtraActions` inside it still carried the very parameter that shape existed to drop.
### 2. Write tools are withheld unless you ask for them
`BUNNY_READONLY` defaults to on. In that mode the write-capable tools are **never registered** — absent from `tools/list`, not merely annotated as risky. An agent cannot call a tool it cannot see, and the MCP `destructiveHint` is advice to a client, not a control.
The gate fails closed: a tool is registered in read-only mode only if it declares `readOnlyHint: true`. A new tool whose author forgot its annotations counts as a writer and is withheld.
```bash
BUNNY_READONLY=0 # register the write tools too — 0/false/no/off, nothing else
```
### Errors are projected too
A non-2xx response never reaches the response interceptor — axios routes it to the rejection handler — so error bodies get their own boundary. Bunny quotes submitted values back in validation messages, and what these tools submit includes edge-script secrets, so the rule keys on the **request**: a request that carried no body cannot have its own payload echoed at it and keeps its message; a request that carried one has the message withheld, with the status and `ErrorKey` still saying what went wrong.
### Diagnostics keep the sentence and lose the target
An origin error log and a transcoding failure both quote the request that failed, and that request is the one an operator signs. Those fields are kept — a diagnostic that will not say what failed is not worth returning — but the target inside them is **withheld whole**, not edited:
```
failed fetching https://svc:pw@origin/x?token=secret after 10s
↓
failed fetching (withheld: URL) after 10s
```
A whitespace-delimited token is withheld when it carries an `@`, or a `?`/`#` with anything attached to it — either side. That is what separates a query or fragment from ordinary punctuation: `why? because` has a space after the mark, while `callback?token=secret` and a bare `#access_token=x` do not. Nothing is parsed, so there is no interior for a new URL shape to hide in — nine review findings were spent teaching an earlier reducer the shapes prose can take, and each one found the shape the last had not met.
A fragment goes even when it looks like a section number. `#3` reads as a reference and `#123456` reads as a PIN, but they are the same string with different digits, so no rule can tell them apart; both are withheld rather than guessed at.
A token with none of those marks is returned exactly as written, so `https://origin.example/ok`, `origin.example/file` and `3.5` are untouched: a plain target carries nothing, and which host failed is most of a diagnostic's value.
The **structured** target fields — a log's `Url` and `Path` — are reduced rather than withheld, because a field that IS a URL can be cut precisely.
What this does not catch, said plainly: a secret embedded in a path segment, as in `/download/sk_live_x/file`. Nothing short of understanding the operator's own URL scheme would.
### Edge-script source is withheld by default
`/compute/script/<id>/code` returns the script's source, and source carries hard-coded keys about as readily as any other operator-authored text — `CustomHTML` is dropped for exactly that reason. So the body is withheld and the response says how to release it:
```bash
BUNNY_ALLOW_SOURCE=1 # return edge-script source — 1/true/yes/on, nothing else
```
More generally, a non-JSON body on the management API no longer gets a free pass. It passes only where a route declares it may; anything else raises, naming the path. The blanket "non-JSON means it's a file download" exemption was the hole this closed.
### Credential scoping
Bunny does not offer scoped API keys. The [authentication docs](https://bunny.net/docs/api-reference/authentication) say it plainly: *"You can have only one API key associated with your account."* The dashboard's **Account → API** page can only view and rotate that key, and while the `/apikey` endpoint models multiple keys with roles, neither the UI nor the docs expose creating one. So the key this server runs with is the account key, and the mitigations are:
- **`BUNNY_API_KEY_FILE`** — point it at a mode-`0600` file and the server reads the key at spawn, so no MCP client config ever holds the value. `BUNNY_API_KEY` still works and wins when both are set.
- **`BUNNY_READONLY`** stays on, so write tools are never registered.
- The response projection keeps the key - and every other credential Bunny echoes - out of the transcript. Rotate the key from that same page if it is ever exposed; a rotation invalidates the old value immediately.
---
## Features
| Tool | Description | Data Source | Mode |
|------|-------------|-------------|------|
| `bunny_get_account` | Get account details and balance | bunny.net API | read |
| `bunny_get_billing_summary` | Get billing summary with charges | bunny.net API | read |
| `bunny_get_statistics` | Get CDN statistics (bandwidth, requests, cache hit rate) | bunny.net API | read |
| `bunny_global_search` | Search across all resources | bunny.net API | read |
| `bunny_purge_url` | Purge a URL from CDN cache | bunny.net API | write |
| `bunny_list_regions` | List CDN edge regions | bunny.net API | read |
| `bunny_list_countries` | List countries for geo-blocking | bunny.net API | read |
| `bunny_list_pull_zones` | List pull zones with search and pagination | bunny.net API | read |
| `bunny_get_pull_zone` | Get pull zone details | bunny.net API | read |
| `bunny_create_pull_zone` | Create a pull zone | bunny.net API | write |
| `bunny_update_pull_zone` | Update pull zone settings | bunny.net API | write |
| `bunny_delete_pull_zone` | Delete a pull zone | bunny.net API | write |
| `bunny_purge_pull_zone_cache` | Purge entire pull zone cache | bunny.net API | write |
| `bunny_manage_pull_zone_hostnames` | Add or remove custom hostnames | bunny.net API | write |
| `bunny_manage_edge_rules` | Add, update, delete, or toggle edge rules | bunny.net API | write |
| `bunny_list_dns_zones` | List DNS zones | bunny.net API | read |
| `bunny_get_dns_zone` | Get DNS zone with all records | bunny.net API | read |
| `bunny_create_dns_zone` | Create a DNS zone | bunny.net API | write |
| `bunny_update_dns_zone` | Update DNS zone settings | bunny.net API | write |
| `bunny_delete_dns_zone` | Delete a DNS zone | bunny.net API | write |
| `bunny_manage_dns_record` | Add, update, or delete DNS records | bunny.net API | write |
| `bunny_get_dns_statistics` | Get DNS query statistics | bunny.net API | read |
| `bunny_list_storage_zones` | List storage zones | bunny.net API | read |
| `bunny_get_storage_zone` | Get storage zone details | bunny.net API | read |
| `bunny_create_storage_zone` | Create a storage zone | bunny.net API | write |
| `bunny_get_storage_zone_statistics` | Get storage zone usage statistics | bunny.net API | read |
| `bunny_list_storage_files` | List files and directories | Storage API | read |
| `bunny_download_storage_file` | Download file content | Storage API | read |
| `bunny_delete_storage_file` | Delete a file or directory | Storage API | write |
| `bunny_list_video_libraries` | List video libraries | bunny.net API | read |
| `bunny_get_video_library` | Get library details | bunny.net API | read |
| `bunny_create_video_library` | Create a video library | bunny.net API | write |
| `bunny_update_video_library` | Update library settings | bunny.net API | write |
| `bunny_list_videos` | List videos with search and pagination | Stream API | read |
| `bunny_get_video` | Get video details | Stream API | read |
| `bunny_create_video` | Create video object, optionally fetch from URL | Stream API | write |
| `bunny_update_video` | Update video metadata | Stream API | write |
| `bunny_delete_video` | Delete a video | Stream API | write |
| `bunny_get_video_statistics` | Get view statistics | Stream API | read |
| `bunny_get_video_heatmap` | Get attention heatmap data | Stream API | read |
| `bunny_reencode_video` | Re-encode a video | Stream API | write |
| `bunny_list_collections` | List video collections | Stream API | read |
| `bunny_get_collection` | Get collection details | Stream API | read |
| `bunny_manage_collection` | Create, update, or delete collections | Stream API | write |
| `bunny_list_edge_scripts` | List edge scripts | bunny.net API | read |
| `bunny_get_edge_script` | Get script details | bunny.net API | read |
| `bunny_get_edge_script_code` | Get script source code | bunny.net API | read |
| `bunny_set_edge_script_code` | Upload script code (saved as draft) | bunny.net API | write |
| `bunny_manage_edge_script` | Create, update, or delete scripts | bunny.net API | write |
| `bunny_publish_edge_script` | Publish a release to edge servers | bunny.net API | write |
| `bunny_list_edge_script_variables` | List a script's environment variable names | bunny.net API | read |
| `bunny_manage_edge_script_variables` | Manage environment variables and secrets | bunny.net API | write |
| `bunny_list_shield_zones` | List shield security zones | bunny.net API | read |
| `bunny_get_shield_zone` | Get zone by shield zone ID or pull zone ID | bunny.net API | read |
| `bunny_get_waf_rules` | Get WAF rules and profiles | bunny.net API | read |
| `bunny_manage_waf_custom_rule` | Create, update, or delete custom WAF rules | bunny.net API | write |
| `bunny_list_rate_limit_rules` | List rate limiting rules | bunny.net API | read |
| `bunny_manage_rate_limit_rule` | Create, update, or delete rate limit rules | bunny.net API | write |
| `bunny_get_shield_metrics` | Get security metrics overview | bunny.net API | read |
| `bunny_read_bot_detection` | Read bot detection settings | bunny.net API | read |
| `bunny_get_bot_detection` | Get or update bot detection settings | bunny.net API | write |
| `bunny_list_mc_apps` | List Magic Container applications | bunny.net API | read |
| `bunny_get_mc_app` | Get application details | bunny.net API | read |
| `bunny_get_mc_app_overview` | Get app overview with real-time metrics | bunny.net API | read |
| `bunny_manage_mc_app` | Create, update, or delete applications | bunny.net API | write |
| `bunny_mc_app_lifecycle` | Deploy, undeploy, or restart applications | bunny.net API | write |
| `bunny_list_mc_registries` | List container registries | bunny.net API | read |
| `bunny_list_mc_regions` | List deployment regions | bunny.net API | read |
| `bunny_get_mc_app_statistics` | Get application statistics | bunny.net API | read |
| `bunny_get_origin_errors` | Get origin error logs for a pull zone | bunny.net API | read |
**Data sources:** Tools marked **Storage API** require `BUNNY_STORAGE_KEY`. Tools marked **Stream API** require `BUNNY_STREAM_KEY`. All other tools use `BUNNY_API_KEY`.
## Prerequisites
- Node.js >= 18
- A [bunny.net](https://bunny.net) account with an API key
- Optional: Stream library API key (for video tools)
- Optional: Storage zone password (for file tools)
## Setup
No installation needed — just configure your MCP client:
<details>
<summary>VS Code / Copilot</summary>
Add to `.vscode/mcp.json`:
```json
{
"servers": {
"bunny": {
"command": "npx",
"args": ["-y", "github:Digitizers/bunny-mcp"],
"env": {
"BUNNY_API_KEY": "your-api-key"
}
}
}
}
```
</details>
<details>
<summary>Cursor</summary>
Add to `.cursor/mcp.json`:
```json
{
"mcpServers": {
"bunny": {
"command": "npx",
"args": ["-y", "github:Digitizers/bunny-mcp"],
"env": {
"BUNNY_API_KEY": "your-api-key"
}
}
}
}
```
</details>
<details>
<summary>Windsurf</summary>
Add to `~/.codeium/windsurf/mcp_config.json`:
```json
{
"mcpServers": {
"bunny": {
"command": "npx",
"args": ["-y", "github:Digitizers/bunny-mcp"],
"env": {
"BUNNY_API_KEY": "your-api-key"
}
}
}
}
```
</details>
<details>
<summary>Claude Desktop</summary>
Add to `claude_desktop_config.json`:
```json
{
"mcpServers": {
"bunny": {
"command": "npx",
"args": ["-y", "github:Digitizers/bunny-mcp"],
"env": {
"BUNNY_API_KEY": "your-api-key"
}
}
}
}
```
</details>
<details>
<summary>Claude Code</summary>
```bash
claude mcp add --transport stdio bunny -- npx -y github:Digitizers/bunny-mcp
```
Or add to `.mcp.json` (shared with team):
```json
{
"mcpServers": {
"bunny": {
"command": "npx",
"args": ["-y", "github:Digitizers/bunny-mcp"],
"env": {
"BUNNY_API_KEY": "your-api-key"
}
}
}
}
```
</details>
<details>
<summary>Zed</summary>
Add to `settings.json`:
```json
{
"context_servers": {
"bunny": {
"command": "npx",
"args": ["-y", "github:Digitizers/bunny-mcp"],
"env": {
"BUNNY_API_KEY": "your-api-key"
}
}
}
}
```
</details>
<details>
<summary>JetBrains IDEs</summary>
Open **Settings → Tools → AI Assistant → MCP**, click **+**, and paste:
```json
{
"mcpServers": {
"bunny": {
"command": "npx",
"args": ["-y", "github:Digitizers/bunny-mcp"],
"env": {
"BUNNY_API_KEY": "your-api-key"
}
}
}
}
```
</details>
<details>
<summary>Gemini CLI</summary>
```bash
gemini mcp add bunny -- npx -y github:Digitizers/bunny-mcp
```
Or add to `~/.gemini/settings.json`:
```json
{
"mcpServers": {
"bunny": {
"command": "npx",
"args": ["-y", "github:Digitizers/bunny-mcp"],
"env": {
"BUNNY_API_KEY": "your-api-key"
}
}
}
}
```
</details>
<details>
<summary>Other MCP clients</summary>
Any MCP client that supports **stdio** transport can use this server. The command is:
```
npx -y github:Digitizers/bunny-mcp
```
See the [full list of MCP clients](https://modelcontextprotocol.io/clients).
</details>
### Optional environment variables
| Variable | Description |
|----------|-------------|
| `BUNNY_STREAM_KEY` | Video library API key — enables Stream video and collection tools |
| `BUNNY_STORAGE_KEY` | Storage zone password — enables Storage file tools |
| `BUNNY_STORAGE_REGION` | Storage region code (default: empty for Falkenstein) |
| `BUNNY_STORAGE_ZONE` | Default storage zone name |
Add these to the `env` block in your MCP client configuration above.
### Local development
```bash
git clone https://github.com/Digitizers/bunny-mcp.git
cd bunny-mcp
npm install
npm test
node index.js
```
## How It Works
This MCP server connects to the [bunny.net API](https://docs.bunny.net/reference/bunnynet-api-overview) using your API key. The catalog above holds 70 tools, split by which API keys are provided:
- **Core tools** (56 tools) — always available with `BUNNY_API_KEY`
- **Stream tools** (11 tools) — registered when `BUNNY_STREAM_KEY` is set
- **Storage file tools** (3 tools) — registered when `BUNNY_STORAGE_KEY` is set
Those are the totals with the write gate open. **By default `BUNNY_READONLY` is on and 41 of the 70 register** — the 29 write-capable ones are withheld, per [section 2](#2-write-tools-are-withheld-unless-you-ask-for-them). The `Mode` column in the catalog says which is which.
Both counts assume all three keys. With `BUNNY_API_KEY` alone the core tools are all there is: **33** registered read-only, **56** with the gate open.
All read operations are cached in-memory with a short TTL for performance. Every tool includes MCP annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`) so clients can make informed decisions about tool approval.
## License
MIT