← Back to directory
N

Netdata MCP Server

Official
Real-time infrastructure monitoring and anomaly detection.
GitHub source repository ↗
★ 80.5k Stars Category · Other Very popular Source revision afe8fe9fc590
51FMRS · D

This remote MCP server is maintained by Netdata, the upstream observability product owner. It serves Netdata Cloud users with metrics, logs, alerts, and machine-learning anomaly detection. The manifest lists no tool names or client compatibility, so those fields remain empty.

Reliability
7/20
Security and permissions
13/20
Maintenance
14/20
Documentation
8/20
Setup experience
9/20
Read the FMRS scoring method →

The Netdata MCP server provides real-time infrastructure observability through Netdata Cloud, covering metrics, logs, alerts, and machine-learning-based anomaly detection. It is the server listed in server.json and connects to Netdata Cloud over Streamable HTTP.

Setup

Connect over Streamable HTTP to https://app.netdata.cloud/api/v1/mcp and provide Authorization: Bearer {NETDATA_CLOUD_API_TOKEN}. Create the token in app.netdata.cloud under User Settings > API Tokens with scope:mcp. The source does not provide a client-specific configuration format.

Fit and risk

Best for

  • DevOps and infrastructure teams using Netdata Cloud
  • Operators who need real-time monitoring, alerting, and anomaly analysis
  • Teams managing Linux, containerized, or Kubernetes environments

Not for

  • Client environments requiring a local stdio server
  • Users who do not use Netdata or cannot access Netdata Cloud
  • Workflows requiring undocumented write or infrastructure-management operations

Required permissions

  • Requires a Netdata Cloud API token
  • The token must have scope:mcp
  • The client must send authenticated requests to the Netdata Cloud MCP endpoint

Risks and side effects

  • The API token is a secret credential and should not be exposed
  • The server accesses monitoring data through Netdata Cloud, so organizational data-access requirements should be reviewed
  • The source does not document specific tools or write permissions; infrastructure changes should not be assumed

Troubleshooting

  1. Verify the MCP endpoint is https://app.netdata.cloud/api/v1/mcp
  2. Verify the Authorization header uses Bearer token format
  3. Verify the token was created in Netdata Cloud with scope:mcp
  4. Check that the client supports Streamable HTTP
  5. Confirm network access to Netdata Cloud

Use cases

Query infrastructure metrics and logs
Review monitoring alerts
Analyze machine-learning-detected anomalies
Assist with troubleshooting servers, containers, and Kubernetes environments

More servers from this repository