What is the key difference between Blazingcdn MCP and MCP Uptime Kuma?

Blazingcdn MCP belongs to the Monitoring category with local stdio execution, while MCP Uptime Kuma belongs to the Monitoring category with local stdio execution.

How do I install Blazingcdn MCP or MCP Uptime Kuma in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Blazingcdn MCP and MCP Uptime Kuma free or paid?

Blazingcdn MCP operates under a Free / Open Source model (No auth required). MCP Uptime Kuma operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Blazingcdn MCP lists 8 tools with 0 views and 2 GitHub stars. MCP Uptime Kuma lists 22 tools with 1 views and 54 GitHub stars.

Can I use both Blazingcdn MCP and MCP Uptime Kuma together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Blazingcdn MCP vs MCP Uptime Kuma

In-depth architectural comparison of the Blazingcdn MCP and MCP Uptime Kuma MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Blazingcdn MCP

Monitoring · Local stdio

Quality: 56/100 (Good) | Auth: No auth required

MCP Uptime Kuma

Monitoring · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Verdict Summary: Choose Blazingcdn MCP if you need specialized Monitoring tools running via a local process. Choose MCP Uptime Kuma if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Blazingcdn MCP when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: BLAZINGCDN_API_TOKEN, BLAZINGCDN_API_URL, BLAZINGCDN_ALLOW_WRITE, BLAZINGCDN_ALLOW_DELETE.
Primary tools included: list_cdn_resources, get_cdn_resource, purge_cache.

Explore Blazingcdn MCP Details

Choose MCP Uptime Kuma when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_HEADERS.

Feature & Specification Comparison

Specification	Blazingcdn MCP Monitoring	MCP Uptime Kuma Monitoring
Summary
Category & Scope	Monitoring	Monitoring
Quality signal

Tools & Capabilities Breakdown

Blazingcdn MCP Tools (8)

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

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Blazingcdn MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "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 Uptime Kuma Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@davidfuchs/mcp-uptime-kuma",
        "mcp-uptime-kuma-get-jwt"
      ],
      "env": {
        "UPTIME_KUMA_URL": "YOUR_UPTIME_KUMA_URL_HERE",
        "UPTIME_KUMA_USERNAME": "YOUR_UPTIME_KUMA_USERNAME_HERE",
        "UPTIME_KUMA_PASSWORD": "YOUR_UPTIME_KUMA_PASSWORD_HERE",
        "UPTIME_KUMA_2FA_TOKEN": "YOUR_UPTIME_KUMA_2FA_TOKEN_HERE",
        "UPTIME_KUMA_JWT_TOKEN": "YOUR_UPTIME_KUMA_JWT_TOKEN_HERE",
        "UPTIME_KUMA_HEADERS": "YOUR_UPTIME_KUMA_HEADERS_HERE"
      }
    }
  }
}

Frequently Asked Questions

Blazingcdn MCP is categorized under Monitoring and uses a local stdio subprocess. In contrast, MCP Uptime Kuma belongs to Monitoring using local stdio subprocess. Select Blazingcdn MCP when you need capabilities focused on monitoring and MCP Uptime Kuma when you require tools for monitoring.

More alternatives to Blazingcdn MCP More alternatives to MCP Uptime Kuma Monitoring category hub