Blazingcdn MCP vs Datadog MCP Server
A side-by-side look at the Blazingcdn MCP and Datadog MCP Server 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 Datadog 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.
Choose Datadog 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:
DD_API_KEY, DD_APP_KEY, DD_SITE, MCP_DEFAULT_LIMIT, MCP_DEFAULT_LOG_LINES, MCP_DEFAULT_METRIC_POINTS, MCP_DEFAULT_TIME_RANGE, MCP_TRANSPORT. - You want tools like
monitors, dashboards, logs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 55/100 · Good | 64/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 | DD_API_KEYDD_APP_KEYDD_SITEMCP_DEFAULT_LIMITMCP_DEFAULT_LOG_LINESMCP_DEFAULT_METRIC_POINTSMCP_DEFAULT_TIME_RANGEMCP_TRANSPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 6 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 8 | 22 |
| Full listing | View Blazingcdn MCP | View Datadog 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
Datadog MCP Server tools 22
monitorsList monitors with optional filtersdashboardsList all dashboardslogsSearch logs with query syntax and filterslogs_pipelinesInspect log processing pipelines and their processorslogs_indexesInspect indexes (filter, retention, Flex tier, exclusion filters); `create`/`delete` are UI-only per Datadog and not exposedlogs_archivesInspect log archives (S3 / GCS / Azure destinations); per-provider credential fields are forwarded unchangedmetricsQuery timeseries data. Response `meta` includes `rollupRequested` (parsed from `rollup(method, seconds)`, with `methodInferred` flag), `rollupEffective` (interval derived from returned pointlist intervals + deduped `intervalsObserved` for multi-series), and `rollupOverridden: boolean` so callers ca…tracesSearch spans with filterseventsList eventsincidentsList incidentsslosList SLOs. Each item exposes `query`, `monitorIds`, `monitorTags`, `groups`, and a UI `url` so round-trips (get → edit → update) preserve definition fields.syntheticsList synthetic tests- +10 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"
}
}
}
}
Datadog MCP Server
{
"mcpServers": {
"tantiope-datadog-mcp-server": {
"command": "npx",
"args": [
"-y",
"datadog-mcp"
],
"env": {
"DD_API_KEY": "YOUR_DD_API_KEY_HERE",
"DD_APP_KEY": "YOUR_DD_APP_KEY_HERE",
"DD_SITE": "YOUR_DD_SITE_HERE",
"MCP_DEFAULT_LIMIT": "YOUR_MCP_DEFAULT_LIMIT_HERE",
"MCP_DEFAULT_LOG_LINES": "YOUR_MCP_DEFAULT_LOG_LINES_HERE",
"MCP_DEFAULT_METRIC_POINTS": "YOUR_MCP_DEFAULT_METRIC_POINTS_HERE",
"MCP_DEFAULT_TIME_RANGE": "YOUR_MCP_DEFAULT_TIME_RANGE_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE"
}
}
}
}
Frequently asked questions
Blazingcdn MCP is categorized under Monitoring and uses a local stdio subprocess. Datadog MCP Server belongs to Monitoring and uses a local stdio subprocess. Pick Blazingcdn MCP for monitoring work and Datadog 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. Datadog 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 tantiope-datadog-mcp-server 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. Datadog MCP Server has 64/100 (Good) with 3 views, 0 installs and 6 GitHub stars.