Official MCP server for BlazingCDN - AI agents (Claude, Cursor, Windsurf) manage CDN resources, purge cache, query metrics, domains, Cloud Storage and Video CDN
claude mcp add blazingcdn-mcp -- npx -y blazingcdn-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
2 ★ · BlazingCDN/BlazingCDN-MCP · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 2 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository BlazingCDN/BlazingCDN-MCP;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
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 1. **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. 2. **Top up your balance** with at least **$10** right after signing up so your account doesn't go negative while you test. 3. **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 Desktop / Cursor / Windsurf Add to your MCP configuration (claude_desktop_config.json, .cursor/mcp.json, etc.): 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.