Blazingcdn MCP vs MCP Server
A side-by-side look at the Blazingcdn MCP and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MCP ServerMonitoring · Local subprocess (stdio)Local MCP (Model Context Protocol) server for integrating LLMs with Mackerel.60GoodAuth: api key requiredVerdict: choose Blazingcdn MCP for monitoring work as a local process; choose MCP Server for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Blazingcdn MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BLAZINGCDN_API_TOKEN, BLAZINGCDN_API_URL, BLAZINGCDN_ALLOW_WRITE, BLAZINGCDN_ALLOW_DELETE. - You want tools like
list_cdn_resources, get_cdn_resource, purge_cache.
MChoose MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
MACKEREL_APIKEY. - You want tools like
list_alerts, get_alert, get_alert_logs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M MCP Server | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 55/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | BLAZINGCDN_API_TOKENBLAZINGCDN_API_URLBLAZINGCDN_ALLOW_WRITEBLAZINGCDN_ALLOW_DELETE | MACKEREL_APIKEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 7 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 8 | 16 |
| Full listing | View Blazingcdn MCP | View MCP Server |
Tools & capabilities
Blazingcdn MCP tools 8
list_cdn_resourcesList all CDN resources (pull zones)get_cdn_resourceFull settings of one resourcepurge_cachePurge everything or specific URLs; works per-resource or across resources by URLwarmup_cachePre-fetch paths into the cache (per compression method)get_cdn_metricsBandwidth, cache hit, requests, HTTP codes, traffic — by day/hour/minute, filter by region/domainget_prometheus_metricsPrometheus-format metrics for monitoringlist_custom_domainsDomains of a resource / match domains account-widelist_system_dns_zonesSystem DNS zones for CDN hostnames
MCP Server tools 16
list_alertsRetrieve alerts.get_alertRetrieve a specific alert.get_alert_logsRetrieve logs for a specific alert.list_dashboardsRetrieve dashboards.get_dashboardRetrieve a specific dashboard.update_dashboardUpdate a specific dashboard.list_hostsRetrieve hosts.get_host_metricsRetrieve metrics data for a specific host.list_servicesRetrieve services.get_service_metricsRetrieve metrics data for a specific service.list_monitorsRetrieve monitor configurations.get_monitorRetrieve a specific monitor configuration.- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Blazingcdn MCP
{
"mcpServers": {
"blazingcdn-mcp": {
"command": "npx",
"args": [
"-y",
"@blazingcdn/mcp"
],
"env": {
"BLAZINGCDN_API_TOKEN": "YOUR_BLAZINGCDN_API_TOKEN_HERE",
"BLAZINGCDN_API_URL": "YOUR_BLAZINGCDN_API_URL_HERE",
"BLAZINGCDN_ALLOW_WRITE": "YOUR_BLAZINGCDN_ALLOW_WRITE_HERE",
"BLAZINGCDN_ALLOW_DELETE": "YOUR_BLAZINGCDN_ALLOW_DELETE_HERE"
}
}
}
}
MCP Server
{
"mcpServers": {
"mcp-server-180": {
"command": "npx",
"args": [
"-y",
"@mackerel/mcp-server"
],
"env": {
"MACKEREL_APIKEY": "YOUR_MACKEREL_APIKEY_HERE"
}
}
}
}
Frequently asked questions
Blazingcdn MCP is categorized under Monitoring and uses a local stdio subprocess. MCP Server belongs to Monitoring and uses a local stdio subprocess. Pick Blazingcdn MCP for monitoring work and MCP Server for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Blazingcdn MCP has no declared pricing — check the project's own site. MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add blazingcdn-mcp and mcp-server-180 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Blazingcdn MCP has a quality signal of 55/100 (Good) with 1 views, 0 installs and 2 GitHub stars. MCP Server has 60/100 (Good) with 0 views, 0 installs and 7 GitHub stars.