Skip to directory

About Netdata MCP

Netdata's official MCP integration lets AI clients explore metrics, alerts, nodes, logs, and system data available from a Netdata Agent or Parent, or from Netdata Cloud across claimed nodes.

What you can use it for

  • Explore infrastructure nodes and metrics
  • Query metric aggregations and anomaly-related signals
  • Review active alerts and alert history
  • Inspect logs or run system functions where the connected Parent/permissions support them
Connection and setup
Hosting
hosted
Transport
Streamable HTTP
Endpoint
Local process; no hosted endpoint documented
Authentication
Cloud uses a Netdata Cloud API token with scope:mcp. Local Agent/Parent may require its generated MCP API key depending on bearer protection.

Requirements

  • For Cloud: a Netdata Cloud account on a paid plan, a token with scope:mcp, and nodes claimed to the user's Netdata Cloud space.
  • For local Agent/Parent: Netdata Agent v2.6.0 or newer, network access to the chosen host, and possibly the local API key depending on configuration.
  • Some clients that cannot connect to remote HTTP/SSE endpoints need the Netdata `nd-mcp` stdio bridge installed with Netdata.

Setup steps

  1. For Netdata Cloud, sign in to Netdata Cloud, open the profile menu at the lower left → User Settings → API Tokens, create a token with `scope:mcp`, and store it securely. Register `https://app.netdata.cloud/api/v1/mcp` as a Streamable HTTP server and send the token as an Authorization Bearer header. The token itself is not included in catalog configuration.
  2. Cloud MCP requires a paid plan and can see only nodes claimed to that Cloud space. Confirm the intended nodes are claimed before connecting.
  3. For a local Agent or Parent, use its documented endpoint `http://<NETDATA_HOST>:19999/mcp`. The Agent path requires Netdata v2.6.0 or newer. If a client only supports stdio, configure the bundled `nd-mcp` bridge with `--bearer <LOCAL_NETDATA_API_KEY>` and `ws://<NETDATA_HOST>:19999/mcp`; locate the key using the official Netdata instructions on the host that runs Netdata.
  4. Reconnect the client and inspect tools/list. Available data is limited by the selected Cloud space or Agent/Parent topology; a standalone child exposes only its own node, while a parent exposes connected child nodes.
  5. Follow Netdata's official MCP setup guide for the chosen mode and client. Never paste API tokens into chat or commit them in shared configuration.
Tools 13

13 active tool identifiers from the current Netdata source registry; one candidate tool is commented out and excluded. Netdata versions, configuration and hosting mode may alter availability.

  • list_metrics

    Lists available metric contexts, with time-aware filtering and search.

    01
  • get_metrics_details

    Returns metric metadata including units, dimensions, instances, labels, and collection status.

    02
  • list_nodes

    Lists monitored nodes with IDs, hostnames, status, and parent-child relationships.

    03
  • get_nodes_details

    Returns node hardware, OS, capabilities, health, functions, and configuration details.

    04
  • list_functions

    Lists Netdata functions available for execution on nodes.

    05
  • execute_function

    Executes a live data collection function on a selected node.

    06
  • query_metrics

    Queries time-series metrics with time ranges, aggregation, grouping, and filters.

    07
  • find_correlated_metrics

    Finds metrics that changed significantly between incident and baseline periods.

    08
  • find_anomalous_metrics

    Ranks metrics by anomaly rates from Netdata ML models.

    09
  • find_unstable_metrics

    Finds metrics with high variability.

    10
  • list_raised_alerts

    Lists currently active warning and critical alerts across nodes.

    11
  • list_running_alerts

    Lists all alerts, including cleared, undefined, and uninitialized alerts.

    12
  • list_alert_transitions

    Lists recent alert state transitions.

    13
Limitations and notes
  • MCP is read-only.
  • Logs and live system information require an API key and a claimed Agent.
Original sources
  • official agent mcp documentation

    Documents the Agent MCP transport bridge and configuration for local HTTP/SSE endpoints.

  • verified publisher organization avatar

    Netdata organization logo associated with the official Netdata repository and MCP documentation; downloaded, decoded, and visually reviewed on light and dark contact sheets. Selection tier B: official developer/company logo.

  • discovery directory

    Netdata appeared in the awesome-mcp.tools top list; directory ranking was used for discovery only.

  • official maintainer repository

    Official repository documents cloud and local agent endpoints, key-gated sensitive operations, read-only access, and capability-dependent observability surfaces.

Documentation checked 2026-10-28T20:30:00.000Z. Connection has not been runtime tested.