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
N
Netdata MCP Server
Official
Real-time infrastructure monitoring and anomaly detection.
- Category
- Other #142 of 230
- Stars
- ★ 81.0k Very popular
- Transport
- Streamable HTTP
- Runtime
- Hosted (no local runtime)
- Credentials
- API key / credential required
- License
- GPL-3.0
- Last commit
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.
Strongest · Maintenance 14/20 Weakest · Reliability 7/20
Why each score
- Reliability 7/20
- The manifest declares a plausible HTTPS streamable-HTTP endpoint with a required token carrying the MCP scope, so a basic connection path is plausible. However, there is no tool list, initialization or tool-enumeration handshake evidence, tests, error-handling detail, or dependency-control evidence; the static material cannot establish reproducible key paths, so points are deducted.
- Security and permissions 13/20
- The token is sent as an Authorization Bearer credential, is marked secret, and is scoped to MCP; the endpoint uses HTTPS, and the material shows no malicious behavior or default destructive operations. Points are deducted because data boundaries, logging behavior, token lifecycle, fine-grained authorization, confirmation controls, and third-party data flows are not documented; monitoring logs and metrics may contain sensitive information.
- Maintenance 14/20
- The project identifies a GPL-3.0 license, is not archived, and the manifest provides a version, website, and repository ownership. The README also provides security-policy, community, and vulnerability-reporting paths. Points are deducted because the supplied material gives no commit or release cadence, dependency-update evidence, CI status, or MCP-specific maintenance evidence, so sustained maintenance is only partially established.
- Documentation 8/20
- The README gives broad documentation for the Netdata product, deployment platforms, token creation location, and overall capabilities. Points are deducted because it lacks server.json-specific tool parameters, result schemas, limits, quotas, costs, mainstream-client configuration examples, and MCP-specific troubleshooting; the README primarily documents the overall repository and cannot be used to attribute sibling-server tools to this server.
- Setup experience 9/20
- The remote endpoint requires no local runtime, and the manifest identifies where to create the API token, the required scope, and the Authorization header, making the basic setup relatively direct. Points are deducted because there is no complete configuration example for a mainstream MCP client, connection-validation procedure, failure troubleshooting, or platform-compatibility guidance, and no verifiable execution evidence is provided.
Static review · not runListed 2026-07-29
Read the FMRS scoring method →Fit and risk
What it can accessUses the network
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
Setup
Before you start
Runtime：Hosted (no local runtime)
NETDATA_CLOUD_API_TOKEN
Netdata Cloud API token with scope:mcp; create it at app.netdata.cloud > User Settings > API Tokens and use it as a Bearer token for the remote MCP endpoint.
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.
Check that it works
After configuring the remote MCP endpoint https://app.netdata.cloud/api/v1/mcp in your client, refresh the tool list to confirm the Netdata MCP server's tools load (no specific tool names are recorded in the source), then ask a question like "How are my nodes doing?" to verify the connection with the Authorization: Bearer {NETDATA_CLOUD_API_TOKEN} header works.
Troubleshooting
- Verify the MCP endpoint is https://app.netdata.cloud/api/v1/mcp
- Verify the Authorization header uses Bearer token format
- Verify the token was created in Netdata Cloud with scope:mcp
- Check that the client supports Streamable HTTP
- Confirm network access to Netdata Cloud
Things to try
Once connected, you can ask your AI assistant things like:
- Show me the real-time status of all nodes in my Netdata Space.
- Which alerts are currently active across my infrastructure?
- Detect anomalies in my metrics over the last hour.
- Query the CPU usage of my nginx container for the past 24 hours.
Use cases
Query infrastructure metrics and logs
Review monitoring alerts
Analyze machine-learning-detected anomalies
Assist with troubleshooting servers, containers, and Kubernetes environments
Overview
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.
Similar servers
Hevy MCP
77 · B
Manage your Hevy workout data from AI assistants via MCP.
Firecrawl MCP Server
75 · B
Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
BioMCP
75 · B
One binary. One grammar. Evidence from the biomedical sources you already trust.
Compartment
75 · B
Encrypted, fully offline long-term memory for AI agents
More servers from this repository
Source revision dff79a146923 Data synced 2026-10-19 Read the FMRS scoring method