FRENES

Monitoring and observability · MCP server

Netdata: MCP server, setup and security

Netdata is an open-source MCP server published on GitHub that lets an AI agent explore Netdata metrics and logs to analyze root causes. Its repository has 81,115 stars and its last commit is from October 24, 2026 and it is licensed under GPL-3.0.

OfficialActively maintainedRemote serverTop 10% by stars

What Netdata does

According to its repository: “Discovery, exploration, reporting and root cause analysis over Netdata metrics, logs, systems, containers, processes and network connections.”

The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Netdata is listed under Monitoring and observability, a category of 57 servers in the directory, where it ranks #1 by stars.

Topics declared by the repository: monitoring, docker, kubernetes, cncf, prometheus, netdata.

Installing and connecting Netdata

Distribution modes declared in the official MCP registry:

  • remote server (streamable-http): you connect to it by URL, with nothing to install locally

It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: Go. Listed systems: macOS, Windows, Linux.

Security: what to check

Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Netdata. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on June 17, 2013, the netdata/netdata repository has 81,115 stars and 6,690 forks, with 209 open issues. It is one of the most starred servers in the directory. It received changes this month. Version published in the registry: 2.12.2 (October 23, 2026).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.

NetdataNetdata : 81.1K81.1KOpenstatusOpenstatus : 9.2K9.2KOneUptimeOneUptime : 7.8K7.8KMCP grafanaMCP grafana : 3.6K3.6KMarmot Data CatalogMarmot Data Catalog : 623623Watch skillWatch skill : 520520HomebutlerHomebutler : 305305Zabbix MCP serverZabbix MCP server : 261261
GitHub stars of the most followed servers in the category (log scale); Netdata in orange. Checked October 25, 2026.

Verdict

Netdata is one of the most solid servers in its category: followed, maintained and well framed.

Strengths

  • Maintained by the service's own vendor
  • Active project: recent commit
  • Widely followed: 81.1K stars
  • Listed in the official MCP registry
  • Usable remotely, without installation

Frequently asked questions

How do I install Netdata?

Netdata is distributed as a remote server. Add it to your client's MCP configuration (Claude Desktop, Cursor, VS Code…) following the README of netdata/netdata.

Is Netdata free?

The code is published under the GPL-3.0 licence and can be used free of charge.

Is Netdata safe?

No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.

Is it an official server?

Yes: the awesome-mcp-servers list marks it as the service vendor's official implementation.

What are the alternatives to Netdata?

In the same category: MCP grafana, Openstatus, OneUptime, and Homebutler.

Related articles

Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score