Bunny.net MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUNNY_API_KEY | Yes | Account API key from bunny.net Dashboard > Account > API Key | |
| BUNNY_STREAM_API_KEY | Yes | Stream library API key from bunny.net > Stream > Library > API Key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stream_list_videosC | List videos in a Bunny Stream library |
| stream_get_videoC | Get details of a specific video |
| stream_create_videoB | Create a new video object in a library (returns GUID for upload) |
| stream_update_videoC | Update video properties (title, collection, chapters, moments) |
| stream_delete_videoC | Delete a video from a library |
| stream_get_heatmapC | Get video viewer engagement heatmap data |
| stream_add_captionC | Add a caption/subtitle track to a video |
| stream_delete_captionB | Remove a caption track from a video |
| stream_set_thumbnailC | Set a video thumbnail from a specific timestamp |
| stream_reencode_videoC | Trigger re-encoding of a video |
| stream_list_collectionsC | List video collections in a library |
| stream_create_collectionC | Create a new video collection |
| stream_delete_collectionC | Delete a video collection |
| storage_list_filesC | List files and directories in a storage zone path |
| storage_download_fileC | Download/read a file from storage zone (returns text content) |
| storage_upload_fileC | Upload a file to a storage zone (provide base64 content) |
| storage_delete_fileC | Delete a file or directory from a storage zone |
| cdn_list_pullzonesB | List all CDN pull zones |
| cdn_get_pullzoneB | Get pull zone details by ID |
| cdn_create_pullzoneC | Create a new CDN pull zone |
| cdn_update_pullzoneC | Update pull zone settings |
| cdn_delete_pullzoneC | Delete a pull zone |
| cdn_purge_cacheC | Purge all cached content from a pull zone |
| cdn_add_allowed_refererC | Add a domain to the pull zone's allowed referrer list |
| cdn_remove_allowed_refererB | Remove a domain from the pull zone's allowed referrer list |
| cdn_add_blocked_refererC | Add a domain to the pull zone's blocked referrer list |
| cdn_remove_blocked_refererB | Remove a domain from the pull zone's blocked referrer list |
| dns_list_zonesC | List all DNS zones |
| dns_get_zoneC | Get DNS zone details |
| dns_create_zoneC | Create a new DNS zone |
| dns_update_zoneC | Update DNS zone settings |
| dns_delete_zoneC | Delete a DNS zone |
| dns_add_recordC | Add a DNS record to a zone |
| dns_update_recordC | Update an existing DNS record |
| dns_delete_recordC | Delete a DNS record |
| dns_enable_dnssecC | Enable DNSSEC on a DNS zone |
| dns_disable_dnssecC | Disable DNSSEC on a DNS zone |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 37 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized by service domains (CDN, DNS, Storage, Stream), and within each domain, they target specific resources and actions with clear boundaries (e.g., cdn_add_allowed_referer vs. cdn_add_blocked_referer, or stream_create_video vs. stream_update_video).
Tool names follow a highly consistent verb_noun pattern throughout, with a clear prefix for each service domain (cdn_, dns_, storage_, stream_). All tools use snake_case uniformly, and verbs like add, create, delete, get, list, update, etc., are applied predictably across resources.
With 37 tools, the count is borderline high for a single server, potentially feeling heavy. However, given that it covers four distinct service domains (CDN, DNS, Storage, Stream), each with comprehensive operations, it is reasonable but may overwhelm agents due to the volume.
The tool surface provides complete CRUD/lifecycle coverage for each domain. For example, CDN has create, get, list, update, delete for pull zones, plus referrer management and cache purging; DNS has full zone and record management with DNSSEC; Storage has upload, download, list, delete; Stream has video and collection management with additional features like captions, heatmaps, and re-encoding. No obvious gaps are present.