Skip to main content
Glama
fullstuckdev

Bunny.net MCP Server

by fullstuckdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Bunny.net MCP Server

No user-submitted related servers found.

    Related Servers

    • Cloudflare MCP Server

      ry-ops
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to manage Cloudflare resources through natural language, including DNS records, zone management, Workers KV storage, cache purging, and analytics. Supports comprehensive Cloudflare operations with secure API token authentication.
      13
      2
      MIT

    • Porkbun MCP Server

      myroslavtryhubets
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive domain and DNS management through the Porkbun API, including domain registration checks, DNS record operations, URL forwarding, DNSSEC configuration, and SSL certificate management. Provides 27 tools for complete domain administration through natural language interactions.
      3
      MIT

    • rybbit-super-mcp

      Tchoow
      A
      license
      A
      quality
      D
      maintenance
      Enables querying and managing Rybbit Analytics directly from Claude Code, with 48 tools for full CRUD on funnels, goals, and sites, plus real-time statistics, performance metrics, and user journey analysis.
      48
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 37 tools

    Disambiguation5/5

    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).

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources