Netdata#Netdata vs Statuspage

A side-by-side look at the Netdata#Netdata and Statuspage MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Netdata#Netdata logoNetdata#NetdataMonitoringDiscovery, exploration, reporting and root cause analysis using all observability data, including metrics, logs, systems, containers, processes, and network connections52GoodAuth: no auth requiredStatuspage logoStatuspageMonitoring · Local subprocess (stdio)Service status / uptime MCP — Atlassian Statuspage v2.41FairAuth: not declared

Verdict: choose Netdata#Netdata for monitoring work; choose Statuspage for monitoring as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Netdata#Netdata logoChoose Netdata#Netdata when

  • You need dedicated capabilities in the Monitoring domain.
  • Its auth model fits you: No auth required.
Explore Netdata#Netdata

Statuspage logoChoose Statuspage when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
Explore Statuspage

Feature & specification comparison

Rows where the two servers differ are marked.

SpecNetdata#Netdata logoNetdata#NetdataStatuspage logoStatuspage
CategoryMonitoringMonitoring
Quality signal52/100 · Good41/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars81,0600
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Netdata#Netdata tools

No tool names declared yet. Check the project README from the listing page.

Statuspage tools

No tool names declared yet. Check the project README from 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.

Netdata#Netdata

No confirmed install command for Netdata#Netdata yet — follow the setup steps linked from its listing page rather than a guessed package name.

Statuspage

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "statuspage": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-statuspage"
      ]
    }
  }
}

Frequently asked questions

Netdata#Netdata is categorized under Monitoring and uses an install path we have not confirmed yet. Statuspage belongs to Monitoring and uses a local stdio subprocess. Pick Netdata#Netdata for monitoring work and Statuspage 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. Netdata#Netdata has no confirmed install command yet — follow its own setup instructions.

Netdata#Netdata is listed as free. Auth: no auth required. Statuspage has no declared pricing — check the project's own site. 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 netdata-netdata-netdata and statuspage as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Netdata#Netdata has a quality signal of 52/100 (Good) with 3 views, 0 installs and 81,060 GitHub stars. Statuspage has 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.