How do I install Blazingcdn?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Blazingcdn need an API key?

The publisher lists these environment variables: BLAZINGCDN_API_TOKEN, BLAZINGCDN_ALLOW_WRITE, BLAZINGCDN_ALLOW_DELETE.

What transport does Blazingcdn use?

Blazingcdn runs locally over stdio.

When was Blazingcdn last checked?

Last checked 2026-11-08. Manage BlazingCDN from AI agents: CDN zones, cache, metrics, domains, cloud storage and video CDN

Blazingcdn MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @blazingcdn/[email protected]

Credentials from the publisher

BLAZINGCDN_API_TOKEN — BlazingCDN API token (panel: client.blazingcdn.com/api, create new API credentials)
BLAZINGCDN_ALLOW_WRITE — Allow changes: true lets the agent create and change CDN settings
BLAZINGCDN_ALLOW_DELETE — Allow deleting: true lets the agent delete custom domains and Video CDN resources

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1BLAZINGCDN_API_TOKEN=<secret> BLAZINGCDN_ALLOW_WRITE=<value> BLAZINGCDN_ALLOW_DELETE=<value> claude mcp add io.github.blazingcdn-blazingcdn-mcp -- npx -y @blazingcdn/mcp@0.1.6

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.blazingcdn-blazingcdn-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "@blazingcdn/[email protected]"8      ],9      "env": {10        "BLAZINGCDN_API_TOKEN": "<secret>",11        "BLAZINGCDN_ALLOW_WRITE": "<value>",12        "BLAZINGCDN_ALLOW_DELETE": "<value>"13      }14    }15  }16}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.1.6

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

BlazingCDN MCP Server

Official Model Context Protocol server for BlazingCDN. Lets AI agents (Claude, Cursor, Windsurf and any other MCP client) manage your CDN: list and configure resources, purge and warm up cache, query traffic metrics, manage custom domains, cloud storage and the Video CDN.

BlazingCDN is a CDN for video, software & sports media — best for videos, streaming (HLS/DASH), software distribution, games and updates, images, audio, archives and other large files. Built for high-volume projects pushing 5 TB+ per month.

Highlights

52 tools covering Anycast CDN, cache operations, metrics, custom domains, Cloud Storage and Video CDN
Safe by default — starts in read-only mode (plus cache purge/warmup); create/update and delete operations are opt-in via environment flags
No install required — runs with npx
Talks directly to the BlazingCDN API (wapi.blazingcdn.com) with your API token; nothing else sits in between

Getting an account and API token

Sign up at blazingcdn.com — every new account starts with a 14-day trial. The trial is time-limited only: there is no free traffic included, traffic used during the trial is billed at the regular $5/TB rate.
Top up your balance with at least $10 right after signing up so your account doesn't go negative while you test.
Create an API access token: in the BlazingCDN panel open API → create new API credentials (or POST /api/v1/access_tokens).

Pricing (Flex plan)

After the trial you are on the pay-as-you-go Flex plan with a $25/month minimum, which covers your first 5 TB. Traffic is billed on a progressive scale:

Monthly traffic	Price per TB
First 5 TB	$5.00
5–25 TB	$4.50
25–100 TB	$4.00
100–500 TB	$3.50
500–1000 TB	$3.00
1000–1500 TB	$2.50

All plans include custom domains, unlimited requests, origin shield, URL signatures, free SSL and geo allow/block lists — no per-feature surcharges. Pushing more than 100 TB/month? Contact BlazingCDN to request custom volume pricing.

Quick start

Claude Desktop — one-click install (no terminal needed)

Download the latest .mcpb bundle from Releases and double-click it — Claude Desktop asks for your API token and shows two checkboxes: Allow changes (create and change CDN settings) and Allow deleting (custom domains and Video CDN resources). Both are off by default, so the server starts read-only. Node.js is not required.

Claude Code

claude mcp add blazingcdn --env BLAZINGCDN_API_TOKEN=your-token -- npx -y @blazingcdn/mcp

Claude Desktop / Cursor / Windsurf

Add to your MCP configuration (claude_desktop_config.json, .cursor/mcp.json, etc.):

{
  "mcpServers": {
    "blazingcdn": {
      "command": "npx",
      "args": ["-y", "@blazingcdn/mcp"],
      "env": {
        "BLAZINGCDN_API_TOKEN": "your-token"
      }
    }
  }
}

Running from GitHub instead of npm also works: replace "args" with ["-y", "github:BlazingCDN/BlazingCDN-MCP"].

Configuration

Environment variable	Required	Description
`BLAZINGCDN_API_TOKEN`	yes	API access token (Bearer)
`BLAZINGCDN_API_URL`	no	API base URL, default `https://wapi.blazingcdn.com`
`BLAZINGCDN_ALLOW_WRITE`	no	`1` enables create/update tools
`BLAZINGCDN_ALLOW_DELETE`	no	`1` enables delete tools (`delete_custom_domain`, `delete_vcdn_resource`)

Permission model

Mode	Tools	What agents can do
default	29	Read everything + purge/warm up cache
`BLAZINGCDN_ALLOW_WRITE=1`	50	…plus create/update CDN resources, domains, buckets, Video CDN
…`+ BLAZINGCDN_ALLOW_DELETE=1`	52	…plus delete custom domains and vCDN resources

Deleting CDN resources (pull zones), buckets, external storages, accounts or users is not implemented at all — those operations cannot be triggered through this server in any mode.

When a feature is switched off

Every setting this server can change is also a switch in the customer panel. If you ask for something that is off on your resource — image processing, HLS/DASH support, origin shield — the agent tells you exactly where to flip it (client.blazingcdn.com/anycast_cdn/<resource_id>/<tab>), or, with BLAZINGCDN_ALLOW_WRITE=1, offers to turn it on for you and waits for your confirmation.

Tools

Anycast CDN

Tool	Description
`list_cdn_resources`	List all CDN resources (pull zones)
`get_cdn_resource`	Full settings of one resource
`purge_cache`	Purge everything or specific URLs; works per-resource or across resources by URL
`warmup_cache`	Pre-fetch paths into the cache (per compression method)
`get_cdn_metrics`	Bandwidth, cache hit, requests, HTTP codes, traffic — by day/hour/minute, filter by region/domain
`get_prometheus_metrics`	Prometheus-format metrics for monitoring
`create_cdn_resource` ✏️	Create a pull zone (origin, bucket or external storage)
`update_cdn_resource` ✏️	TTLs, compression, origin shield, HTTPS, access protection, HLS/DASH, image processing, Locations Mode, …
`bulk_update_cdn_resources` ✏️	Same settings on several resources
`update_cdn_locations` ✏️	Per-path cache rules and image presets (needs Locations Mode `extended`)

Domains & DNS

Tool	Description
`list_custom_domains` / `search_custom_domains`	Domains of a resource / match domains account-wide
`list_system_dns_zones`	System DNS zones for CDN hostnames
`add_custom_domain` ✏️ / `update_custom_domain` ✏️	Attach domains, manage SSL (auto SSL / certificate)
`delete_custom_domain` 🗑️	Remove a custom domain

Cloud Storage

list_buckets, get_bucket, get_bucket_metrics, get_storage_info, create_bucket ✏️, update_bucket ✏️, list_external_storages, get_external_storage, create_external_storage ✏️, update_external_storage ✏️, test_external_storage_connection ✏️

A bucket used as a CDN resource origin must be of type cdn — create_bucket creates that type by default (private buckets cannot be attached to a pull zone). Pass protocol: "s3" for an S3-compatible bucket; the protocol cannot be changed after creation.

Video CDN

list_vcdn_resources, get_vcdn_resource, get_vcdn_statistics (totals, timeseries, by domain, top domains, HTTP codes, bandwidth, cache/storage), list_vcdn_domains, get_vcdn_domain, list_vcdn_files, get_vcdn_files_total, list_ftp_logins, list_auto_imports, get_vcdn_proxy, get_vcdn_ftp_settings, get_vcdn_settings, create_vcdn_resource ✏️, update_vcdn_resource ✏️, create_vcdn_domain ✏️, update_vcdn_domain ✏️, upload_vcdn_file ✏️, manage_auto_import ✏️, update_vcdn_proxy ✏️, update_vcdn_ftp_settings ✏️, manage_ftp_login ✏️, update_vcdn_settings ✏️, delete_vcdn_resource 🗑️

Docs & pricing

search_docs — search BlazingCDN documentation and product pages. estimate_traffic_cost — calculate the monthly Flex-plan cost for a given traffic volume (progressive tiers, offline).

✏️ requires BLAZINGCDN_ALLOW_WRITE=1 · 🗑️ requires BLAZINGCDN_ALLOW_DELETE=1

Example prompts

"What's my CDN bandwidth this month, broken down by day?"
"Purge /images/* on the blazingcdn.com resource"
"Create a CDN resource for origin https://example.com and attach cdn.example.com with auto SSL"
"Show HTTP 5xx rates for the last 24 hours per region"
"Warm up /video/intro.mp4 with brotli compression"
"How much would 190 TB/month cost on BlazingCDN?"
"Turn on image processing for the shop-images resource and give me a 200×200 thumbnail URL for /images/iphone.jpg"

HTTP transport (self-hosting)

The server also speaks Streamable HTTP for remote deployments:

BLAZINGCDN_ALLOW_WRITE=1 npx -y @blazingcdn/mcp --transport http --port 8462

In HTTP mode the server is stateless and each request must carry the caller's BlazingCDN API token as Authorization: Bearer <token> (an env BLAZINGCDN_API_TOKEN acts as fallback). Put it behind TLS (reverse proxy) before exposing it anywhere.

Development

npm install
npm test        # vitest
npm run build   # tsc -> dist/
npx @modelcontextprotocol/inspector node dist/index.js   # interactive inspector

Privacy Policy

The server collects nothing: no telemetry, no analytics, no third-party calls. Your API token stays in process memory and is sent only to the BlazingCDN API over HTTPS. Full policy: PRIVACY.md · service-level data handling: BlazingCDN Legal Information.

Security notes

The API token is read from the environment and sent only to BLAZINGCDN_API_URL; it is never logged. No middleman, no telemetry.
Read-only by default; destructive operations (zone/bucket/account deletion) are not implemented in any mode.
Tool output is truncated at 60 KB to keep agent contexts healthy.
API requests time out after 30 s (file uploads: 5 min).

Full threat model, limitations and recommendations: SECURITY.md.

Blazingcdn

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Blazingcdn?

Does Blazingcdn need an API key?

What transport does Blazingcdn use?

When was Blazingcdn last checked?

Documentation

BlazingCDN MCP Server

Highlights

Getting an account and API token

Pricing (Flex plan)

Quick start

Claude Desktop — one-click install (no terminal needed)

Claude Code

Claude Desktop / Cursor / Windsurf

Configuration

Permission model

When a feature is switched off

Tools

Anycast CDN

Domains & DNS

Cloud Storage

Video CDN

Docs & pricing

Example prompts

HTTP transport (self-hosting)

Development

Privacy Policy

Security notes

License