Netdata MCP Server – Live Observability for AI

Netdata provides built-in Model Context Protocol servers for AI assistants to query real-time infrastructure observability data. Agents can connect through Netdata Cloud for fleet-wide visibility or directly to a Netdata Agent or Parent for local metrics, alerts, functions, and selected log access.

#observability#monitoring#metrics

Overview

Netdata MCP connects MCP-compatible AI assistants to live Netdata observability data. It is useful when an agent needs current infrastructure context instead of relying on static runbooks, screenshots, or exported dashboard data. Netdata documents two access models: Netdata Cloud MCP for a single hosted endpoint with visibility across claimed nodes, and local Agent or Parent MCP for direct access to a specific Netdata instance on the network.

What the MCP server enables

Through MCP, an AI assistant can discover nodes, inspect metrics, find functions, review active and raised alerts, query time-series data, use ML-powered anomaly context, inspect alert history, and execute supported Netdata functions. Netdata also documents log exploration and function execution through Parent-connected nodes. The practical result is that an assistant can investigate questions such as which nodes are anomalous, which metrics changed together, what alerts transitioned recently, or what live process and network state is visible through Netdata.

When to use it

Use Netdata MCP during incident response, performance debugging, local development troubleshooting, and fleet-level health reviews. Cloud MCP is best when the agent needs broad visibility across all nodes in a Netdata Cloud space without configuring separate endpoints for each system. Local Agent or Parent MCP is better for single-node debugging, private networks, air-gapped environments, or situations where the AI client can reach the Netdata web service directly.

Connection and authentication

Netdata Cloud MCP uses Streamable HTTP at https://app.netdata.cloud/api/v1/mcp and requires a Netdata Cloud API token with scope:mcp sent as an Authorization: Bearer ... header. Local Agent or Parent MCP is built into Netdata v2.6.0 and newer, with direct HTTP and SSE support documented for v2.7.2 and newer. Sensitive local functions require the automatically generated local MCP API key, and newer integrations should pass it in the Authorization header rather than using the legacy query-string form.

Key considerations

Cloud MCP requires a paid Netdata Cloud plan, a token scoped for MCP, and nodes claimed into the Netdata Cloud space. Local MCP requires network access to the Netdata Agent or Parent, and non-HTTPS local endpoints should only be used on trusted networks. Visibility depends on where the assistant connects: Cloud covers the whole space, a Parent covers its children, and a standalone child exposes only that node. Treat MCP credentials like production observability credentials because they can expose operational telemetry and sensitive live system context.

Supported Transports

streamable_http

URL: https://app.netdata.cloud/api/v1/mcp

streamable_http

URL: http://${NETDATA_AGENT_HOST}:19999/mcp

sse

URL: http://${NETDATA_AGENT_HOST}:19999/sse

stdio

Command: npx

Args:

mcp-remote@latest
--http
http://${NETDATA_AGENT_HOST}:19999/mcp
--allow-http
--header
Authorization: Bearer ${NETDATA_MCP_API_KEY}

Frequently Asked Questions

When should an AI agent use the Netdata MCP server?

Use it when an agent needs live infrastructure observability context from Netdata, such as investigating active alerts, comparing metric behavior, reviewing anomaly signals, or troubleshooting a node or fleet during an incident.

What does Netdata MCP add to an AI agent's capabilities?

It gives the agent live access to Netdata node discovery, metrics search, time-series queries, alert information, alert history, metric correlation and anomaly context, supported Netdata functions, and documented log exploration paths.

What can the AI agent access through Netdata MCP?

Access depends on the connection point. Netdata Cloud MCP can cover all nodes connected to the authorized Cloud space, a Netdata Parent can expose connected child nodes, and a standalone Agent exposes that specific node. Sensitive local functions require the local MCP API key.

How is authentication configured for Netdata MCP?

Netdata Cloud MCP requires a Netdata Cloud API token with the mcp scope in the Authorization Bearer header. Local Agent or Parent MCP uses the local MCP API key generated by Netdata, also preferably sent as an Authorization Bearer header rather than as a legacy query-string parameter.

Which transport should be used for Netdata MCP?

Use the Cloud Streamable HTTP endpoint for fleet-wide Netdata Cloud access. Use the local HTTP endpoint when the client can reach a Netdata Agent or Parent directly, SSE when the client needs Netdata's documented server-sent events transport, and the stdio bridge only for clients that cannot connect to HTTP or SSE directly.