bunny.net MCP by usefulapi

Each tool targets a distinct bunny.net resource and action, with clear boundaries between reads, writes, and purges. Overlaps such as bunny_get_dns_zone vs. bunny_list_dns_records are mitigated by explicit filtering/scope differences. There is no apparent risk of confusing one tool with another.

All tools use the same bunny_ prefix and consistent snake_case verb_noun naming, e.g. bunny_add_dns_record, bunny_list_pull_zones, bunny_purge_url. The pattern is predictable across DNS, CDN, storage, video, billing, and account operations.

22 tools is on the heavy side for a single MCP server, though the broad bunny.net product surface (CDN, DNS, storage, Stream, billing, stats) justifies many of them. It falls into the borderline 16-25 range where the set may feel large but not extreme.

Coverage is mostly read-oriented with only selective write operations; many lifecycle actions are missing. For example, DNS lacks delete record/zone and zone updates, pull zones lack create/update/delete and full edge-rule management, storage lacks file operations and zone lifecycle management, and Stream lacks video/library management. These gaps would block common management workflows.