# How to connect BunnyCDN to OpenClaw (paste one key, 126 tools)

> Connect BunnyCDN to OpenClaw with ClawLink: paste your BunnyCDN key once and 126 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/bunnycdn

The usual route to BunnyCDN access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical BunnyCDN setup: install one ClawHub skill, connect BunnyCDN in the browser, and OpenClaw can call real BunnyCDN actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

**Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/bunnycdn

## Setup

It takes three steps to connect OpenClaw to BunnyCDN.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect BunnyCDN** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask OpenClaw in plain English.

**Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect bunnycdn  # connect BunnyCDN (browser OAuth)
npx -y @useclawlink/cli actions bunnycdn  # list available actions
npx -y @useclawlink/cli run bunnycdn <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:

```bash
openclaw plugins install clawhub:clawlink-plugin
```

Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect BunnyCDN in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your BunnyCDN API key once.

Verify the connection by asking OpenClaw:

> Use BunnyCDN to add allowed referer and walk me through the result in plain English.

### Using a different agent?

The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once BunnyCDN is connected in the dashboard, that agent calls the same 126 BunnyCDN tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## BunnyCDN MCP for OpenClaw

Looking for a BunnyCDN MCP server for OpenClaw? ClawLink connects BunnyCDN to OpenClaw and exposes 126 BunnyCDN tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes BunnyCDN integration](https://claw-link.dev/hermes/bunnycdn) works the same way.

## What the OpenClaw BunnyCDN integration can do

126 BunnyCDN tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 126.

### 30 of 126 BunnyCDN tools for OpenClaw

| Tool | What it does |
|---|---|
| **Add allowed referer** `bunnycdn_add_allowed_referer` | Adds a hostname to the allowed referer list for a pull zone |
| **Add blocked ip** `bunnycdn_add_blocked_ip` | Add an IP address to the blocked list of a pull zone |
| **Add blocked referer** `bunnycdn_add_blocked_referer` | Add a blocked referer to a pull zone |
| **Add storage zone** `bunnycdn_add_storage_zone` | Add a new storage zone |
| **Check dns zone availability** `bunnycdn_check_dns_zone_availability` | Check if a DNS zone name is available for registration |
| **Check pull zone availability** `bunnycdn_check_pull_zone_availability` | Check if a pull zone name is available for registration |
| **Check storage zone availability** `bunnycdn_check_storage_zone_availability` | Check if a storage zone name is available |
| **Create live live2** `bunnycdn_create_live_live2` | Retrieve live metrics data for database groups |
| **Generate2fa verification** `bunnycdn_generate2fa_verification` | Generate 2FA verification details for account security setup |
| **Get billing summary** `bunnycdn_get_billing_summary` | Retrieve billing summary with data report for each Pull Zone |
| **Get container config suggestions** `bunnycdn_get_container_config_suggestions` | Get AI-powered configuration suggestions for deploying a container image on BunnyCDN's Magic Containers platform |
| **Get container image digest** `bunnycdn_get_container_image_digest` | Retrieve the digest of a container image from a registry |
| **Get database** `bunnycdn_get_database` | Retrieve details of a specific database by its ID |
| **Get database statistics** `bunnycdn_get_database_statistics` | Retrieve time-series statistics for a Bunny Database instance |
| **Get dns zone details** `bunnycdn_get_dns_zone_details` | Retrieve details of a specific DNS zone by its ID |
| **Get dns zone list** `bunnycdn_get_dns_zone_list` | List all DNS zones in your Bunny CDN account |
| **Get group** `bunnycdn_get_group` | Retrieve details of a specific database group by its ID |
| **Get languages** `bunnycdn_get_languages` | Retrieve the list of languages supported by BunnyCDN's video library |
| **Get limits** `bunnycdn_get_limits` | Retrieve current database limits for the authenticated BunnyCDN account |
| **Get oembed** `bunnycdn_get_oembed` | Retrieve oEmbed metadata for BunnyCDN video embeds |
| **Get optimal base region** `bunnycdn_get_optimal_base_region` | Get the optimal base region for Magic Containers |
| **Get optimizer statistics** `bunnycdn_get_optimizer_statistics` | Retrieve optimizer statistics for a Pull Zone to understand optimization performance |
| **Get origin shield queue statistics** `bunnycdn_get_origin_shield_queue_statistics` | Retrieve Origin Shield Queue Statistics for a specific Pull Zone |
| **Get pull zone** `bunnycdn_get_pull_zone` | Retrieve details of a specific Pull Zone |
| **Get pull zone list** `bunnycdn_get_pull_zone_list` | Retrieve a paginated list of all Pull Zones in your BunnyCDN account |
| **Get safe hop statistics** `bunnycdn_get_safe_hop_statistics` | Retrieve SafeHop statistics for a specific Pull Zone |
| **Get shield bot detection** `bunnycdn_get_shield_bot_detection` | Retrieve bot detection configuration for a specific Shield Zone |
| **Get shield ddos enums** `bunnycdn_get_shield_ddos_enums` | Retrieve available enums for Shield DDoS configuration |
| **Get shield event logs** `bunnycdn_get_shield_event_logs` | Retrieve Shield Event Logs for a specific Shield Zone and date |
| **Get shield metrics bot detection** `bunnycdn_get_shield_metrics_bot_detection` | Retrieve bot detection metrics for a specific Shield Zone |

## Example prompts

**Add Allowed Referer**

> Use BunnyCDN to add allowed referer and walk me through the result in plain English.

**Add Blocked Ip**

> Use BunnyCDN to add blocked ip and walk me through the result in plain English.

**Add Blocked Referer**

> Use BunnyCDN to add blocked referer and walk me through the result in plain English.

**Add Storage Zone**

> Use BunnyCDN to add storage zone and walk me through the result in plain English.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want BunnyCDN working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the BunnyCDN API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected BunnyCDN account becomes available to the agent without you building credential management. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for BunnyCDN. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| **Agent usability** | You still need to expose the right BunnyCDN actions to the runtime in a format your agent can reliably use. | 126 tools for BunnyCDN are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes BunnyCDN to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect BunnyCDN in the browser, and the 126 tools above work from chat. There is no SDK and no config file, and the BunnyCDN key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### OpenClaw installed the BunnyCDN skill but can't call the tools
The ClawHub skill teaches OpenClaw about BunnyCDN, but the calls run through the ClawLink plugin and your connected account. Make sure BunnyCDN is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

### Connection succeeds but no tools appear
Reconnect BunnyCDN from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### "Tool schema not loaded yet" error when calling BunnyCDN tools
BunnyCDN tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every BunnyCDN call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

### BunnyCDN returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

### API key setup works but results look incomplete
Double-check that the API key for BunnyCDN has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw BunnyCDN integration?
Yes. ClawLink is the fastest way to connect OpenClaw to BunnyCDN: link your BunnyCDN account once in the browser and OpenClaw can call the BunnyCDN API through 126 ready-made tools — no custom code or token handling.

### How do I add BunnyCDN to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink BunnyCDN skill from ClawHub, then you click Connect in the dashboard to authorize BunnyCDN. OpenClaw calls the tools from the next message — no config files, and the BunnyCDN key you paste is stored server-side instead of in your environment.

### How long does it take to connect BunnyCDN to OpenClaw?
About two minutes. Sign in, click Connect next to BunnyCDN in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring BunnyCDN up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want BunnyCDN working from chat.

### OpenClaw installed the BunnyCDN skill but can't call the tools
The ClawHub skill teaches OpenClaw about BunnyCDN, but the calls run through the ClawLink plugin and your connected account. Make sure BunnyCDN is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

## Related

- [GitHub tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows
- [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services
- [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.
