A side-by-side look at the Blazingcdn MCP and Dynatrace MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Blazingcdn MCP for monitoring work as a local process; choose Dynatrace MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
BLAZINGCDN_API_TOKEN, BLAZINGCDN_API_URL, BLAZINGCDN_ALLOW_WRITE, BLAZINGCDN_ALLOW_DELETE.list_cdn_resources, get_cdn_resource, purge_cache.DT_ENVIRONMENT, DT_MCP_TOKEN_STORAGE, DT_GRAIL_QUERY_BUDGET_GB.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 55/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | BLAZINGCDN_API_TOKENBLAZINGCDN_API_URLBLAZINGCDN_ALLOW_WRITEBLAZINGCDN_ALLOW_DELETE | DT_ENVIRONMENTDT_MCP_TOKEN_STORAGEDT_GRAIL_QUERY_BUDGET_GB |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 137 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Blazingcdn MCP | View Dynatrace MCP |
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 hostnamesNo tool names declared yet. Check the project README from the listing page.
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.
{
"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"
}
}
}
}
{
"mcpServers": {
"dynatrace-oss-dynatrace-mcp": {
"command": "npx",
"args": [
"-y",
"@dynatrace-oss/dynatrace-mcp-server"
],
"env": {
"DT_ENVIRONMENT": "YOUR_DT_ENVIRONMENT_HERE",
"DT_MCP_TOKEN_STORAGE": "YOUR_DT_MCP_TOKEN_STORAGE_HERE",
"DT_GRAIL_QUERY_BUDGET_GB": "YOUR_DT_GRAIL_QUERY_BUDGET_GB_HERE"
}
}
}
}