Netdata MCP server

Which servers in the official MCP registry are Netdata's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-08

← Back to Netdata

Whose server it is

Registry nameio.github.netdata/mcp-serverpublished by netdata on GitHub

Published under the GitHub organisation netdata, the same one netdata.cloud links from its homepage. The registry ties that namespace to a GitHub sign-in.

When we asked itchecked 2026-10-08

Staterequires sign-inchecked 2026-10-08

On 2026-10-08 the server answered and asked for a sign-in with a Netdata account (OAuth). It shows its tool list only to signed-in users, so we list none here.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "netdata": {
      "type": "http",
      "url": "https://app.netdata.cloud/api/v1/mcp"
    }
  }
}

The first time it connects, the client opens a Netdata sign-in.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.