Blazingcdn MCP

What blazingcdn-mcp MCP server does

The blazingcdn-mcp MCP server exposes BlazingCDN account operations to MCP-compatible agents. It works with Anycast CDN resources, custom domains, system DNS zones, Cloud Storage, and Video CDN resources. The server also provides documentation search and an offline calculator for estimating monthly Flex-plan traffic costs.

For standard CDN resources, agents can list pull zones, inspect full settings, purge all or selected URLs, warm paths into cache, and retrieve delivery metrics. Metrics can cover bandwidth, cache hits, requests, HTTP status codes, and traffic, with time intervals and region or domain filters. Prometheus-format output is available for monitoring workflows.

How it works

The server sends requests directly to the BlazingCDN API at wapi.blazingcdn.com by default. Authentication uses a bearer API token. In its default mode, agents can read account data and perform cache purge or warmup actions. Setting BLAZINGCDN_ALLOW_WRITE=1 enables creation and modification tools; adding BLAZINGCDN_ALLOW_DELETE=1 also enables deletion of custom domains and Video CDN resources.

It supports local stdio execution through npx -y @blazingcdn/mcp. A Streamable HTTP mode is also available for remote deployments. HTTP requests can provide the caller's token in the Authorization header, while the configured environment token serves as a fallback. HTTP deployments should be placed behind TLS before external exposure.

Setup and configuration

Install the blazingcdn-mcp MCP server by adding its npx command to an MCP client configuration, or use the released .mcpb bundle with Claude Desktop. Claude Code, Claude Desktop, Cursor, and Windsurf configurations can pass the token through the environment section. Node.js is not required for the Claude Desktop bundle, but the npx setup requires a Node.js environment capable of running the package.

Required configuration:

• BLAZINGCDN_API_TOKEN: BlazingCDN API access token.
• BLAZINGCDN_API_URL: Optional API base URL; defaults to https://wapi.blazingcdn.com.
• BLAZINGCDN_ALLOW_WRITE: Set to 1 to enable create and update operations.
• BLAZINGCDN_ALLOW_DELETE: Set to 1 to enable supported delete operations.

Tools and capabilities

The server includes tools for:

• Listing and inspecting CDN resources, updating settings, applying bulk changes, and configuring path-based cache rules.
• Purging or warming cache and querying interval-based metrics, including regional and domain breakdowns.
• Searching custom domains and managing domain attachment and SSL settings when write access is enabled.
• Listing, inspecting, creating, and updating buckets and external storage connections.
• Inspecting and managing Video CDN resources, domains, files, imports, proxy settings, FTP settings, and video configuration.
• Searching BlazingCDN documentation and calculating progressive Flex-plan traffic costs locally.

Limitations and notes

Deleting CDN pull zones, buckets, external storages, accounts, and users is not implemented. Delete access only covers custom domains and Video CDN resources. A bucket used as a CDN origin must use the cdn type; private buckets cannot attach to a pull zone. S3-compatible buckets can be created with the S3 protocol, which cannot be changed later.

The server does not collect telemetry, analytics, or make third-party calls. The API token remains in process memory and is sent to BlazingCDN over HTTPS. Enabling write or delete permissions expands what an agent can change, so those flags should be configured deliberately.