原型 · 预览版：收录官方注册中心里的全部服务器，每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚
新手模式 开
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch
☰ 菜单设置
新手模式 开
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch

Netdata

作者：netdata版本 2.12.3i★ –i在云端运行
注册名称io.github.netdata/mcp-server

安装

概览

作者提供的说明（英文原文）

Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在云端运行
  • 传输方式: Streamable HTTP
  • 分类: 开发者工具
  • 你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

你用的是哪个应用？

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

claude mcp add --transport http netdata https://app.netdata.cloud/api/v1/mcp --header 'Authorization: Bearer {NETDATA_CLOUD_API_TOKEN}'

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "netdata": {
      "url": "https://app.netdata.cloud/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer {NETDATA_CLOUD_API_TOKEN}"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "netdata": {
      "type": "http",
      "url": "https://app.netdata.cloud/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer {NETDATA_CLOUD_API_TOKEN}"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

  • Authorization 机密 必填 HTTP header
    Netdata Cloud API token with scope:mcp

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

服务器要求先登录，才会列出它的工具。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 netdata 验证，该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • ✓ 通过

    端点有响应

    在 92 毫秒内响应（HTTP 401）

  • ! 注意

    使用 OAuth 登录

    需要你自己复制粘贴密钥或令牌

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查；我们会在检查端点时读取工具列表

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 1389 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1389 个服务器的 95% 更新
  • 基础检查结果等于或优于此分类中其他 1389 个服务器的 24%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Netdata 安全吗？

它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：Authorization

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2.12.3）于前天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT3天前更新
安装

Desktop Commander

作者：wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT15天前更新
安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Netdata MCP

All Netdata Agents and Parents (v2.6.0+) are Model Context Protocol (MCP) servers, enabling AI assistants to interact with your infrastructure monitoring data.

Every Netdata Agent and Parent includes an MCP server, listening at same port the dashboard is listening at (default: 19999).

Netdata provides comprehensive access to all available observability data through MCP, including complete metadata:

  • Node Discovery - Hardware specifications, operating system details, version information, streaming topology, and associated metadata
  • Metrics Discovery - Full-text search capabilities across contexts, instances, dimensions, and labels
  • Function Discovery - Access to system functions including processes, network-connections, streaming, systemd-journal, windows-events, etc.
  • Alert Discovery - Real-time visibility into active and raised alerts
  • Metrics Queries - Complex aggregations and groupings with ML-powered anomaly detection
  • Metrics Scoring - Root cause analysis leveraging anomaly detection and metric correlations
  • Alert History - Complete alert transition logs and state changes
  • Function Execution - Execute Netdata functions on any connected node (requires Netdata Parent)
  • Log Exploration - Access logs from any connected node (requires Netdata Parent)

For sensitive features currently protected by Netdata Cloud SSO, a temporary MCP API key is generated on each Netdata instance. When presented via the Authorization: Bearer header, this key unlocks access to sensitive data and protected functions (like systemd-journal, windows-events and processes). This temporary API key mechanism will eventually be replaced with a new authentication system integrated with Netdata Cloud.

AI assistants have different visibility depending on where they connect:

  • Netdata Cloud: (coming soon) Full visibility across all nodes in your infrastructure
  • Netdata Parent Node: Visibility across all child nodes connected to that parent
  • Netdata Child/Standalone Node: Visibility only into that specific node

Transport Options

Netdata implements the MCP protocol with multiple transport options:

TransportEndpointUse CaseVersion Requirement
WebSocketws://YOUR_IP:19999/mcpOriginal transport, requires nd-mcp bridge for stdio clientsv2.6.0+
HTTP Streamablehttp://YOUR_IP:19999/mcpDirect connection from AI clients supporting HTTPv2.7.2+
SSEhttp://YOUR_IP:19999/sseServer-Sent Events for real-time streamingv2.7.2+
  • Direct Connection (v2.7.2+): AI clients that support HTTP or SSE transports can connect directly to Netdata
  • Bridge Required: AI clients that only support stdio need the nd-mcp (stdio-to-websocket) or mcp-remote (stdio-to-http or stdio-to-sse) bridge
Official MCP Remote Client (mcp-remote)

If your AI client doesn't support HTTP/SSE directly and you don't want to use nd-mcp, you can use the official MCP remote client (requires Netdata v2.7.2+):

# Export your MCP key once per shell

export NETDATA_MCP_API_KEY="$(cat /var/lib/netdata/mcp_dev_preview_api_key)"

For HTTP transport

npx mcp-remote@latest --http http://YOUR_NETDATA_IP:19999/mcp \ --allow-http \ --header "Authorization: Bearer $NETDATA_MCP_API_KEY"

For SSE transport

npx mcp-remote@latest --sse http://YOUR_NETDATA_IP:19999/mcp \ --allow-http \ --header "Authorization: Bearer $NETDATA_MCP_API_KEY"

Note: The --allow-http flag is required for non-HTTPS connections. Only use this on trusted networks as traffic will not be encrypted.

Finding the nd-mcp Bridge

Note: With the new HTTP and SSE transports, many AI clients can now connect directly to Netdata without nd-mcp. Check your AI client's documentation to see if it supports direct HTTP or SSE connections.

The nd-mcp bridge is only needed for AI clients that:

  • Only support stdio communication (like some desktop applications)
  • Cannot use HTTP or SSE transports directly
  • Cannot use npx mcp-remote@latest

The nd-mcp bridge needs to be available on your desktop or laptop where your AI client runs. Since most users run Netdata on remote servers rather than their local machines, you have two options:

  1. If you have Netdata installed locally - Use the existing nd-mcp
  2. If Netdata is only on remote servers - Build nd-mcp on your desktop/laptop
Option 1: Using Existing nd-mcp

If you have Netdata installed on your desktop/laptop, find the existing bridge:

Linux
# Try these locations in order:

which nd-mcp ls -la /usr/sbin/nd-mcp ls -la /usr/bin/nd-mcp ls -la /opt/netdata/usr/bin/nd-mcp ls -la /usr/local/bin/nd-mcp ls -la /usr/local/netdata/usr/bin/nd-mcp

Or search for it:

find / -name "nd-mcp" 2>/dev/null

Common locations:

  • Native packages (apt, yum, etc.): /usr/sbin/nd-mcp or /usr/bin/nd-mcp
  • Static installations: /opt/netdata/usr/bin/nd-mcp
  • Built from source: /usr/local/netdata/usr/bin/nd-mcp
macOS
# Try these locations:

which nd-mcp ls -la /usr/local/bin/nd-mcp ls -la /usr/local/netdata/usr/bin/nd-mcp ls -la /opt/homebrew/bin/nd-mcp

Or search for it:

find / -name "nd-mcp" 2>/dev/null

Windows
# Check common locations:

dir "C:\Program Files\Netdata\usr\bin\nd-mcp.exe" dir "C:\Netdata\usr\bin\nd-mcp.exe"

Or search for it:

where nd-mcp.exe

Option 2: Building nd-mcp for Your Desktop

If you don't have Netdata installed loca you can build just the nd-mcp bridge. Netdata provides three implementations - choose the one that best fits your environment:

  1. Go bridge (recommended) - Go bridge source code
  • Produces a single binary with no dependencies
  • Creates executable named nd-mcp (nd-mcp.exe on windows)
  • Includes both build.sh and build.bat (for Windows)
  1. Node.js bridge - Node.js bridge source code
  • Good if you already have Node.js installed
  • Creates script named nd-mcp.js
  • Includes build.sh
  1. Python bridge - Python bridge source code
  • Good if you already have Python installed
  • Creates script named nd-mcp.py
  • Includes build.sh

To build:

# Clone the Netdata repository

git clone https://github.com/netdata/netdata.git cd netdata

Choose your preferred implementation

cd src/web/mcp/bridges/stdio-golang/ # or stdio-nodejs/ or stdio-python/

Build the bridge

./build.sh # On Windows with the Go version, use build.bat

The executable will be created with different names:

- Go: nd-mcp

- Node.js: nd-mcp.js

- Python: nd-mcp.py

Test the bridge with your Netdata instance (replace localhost with your Netdata IP)

./nd-mcp ws://localhost:19999/mcp # Go bridge ./nd-mcp.js ws://localhost:19999/mcp # Node.js bridge ./nd-mcp.py ws://localhost:19999/mcp # Python bridge

You should see:

nd-mcp: Connecting to ws://localhost:19999/mcp...

nd-mcp: Connected

Press Ctrl+C to stop the test

Get the absolute path for your AI client configuration

pwd # Shows current directory

Example output: /home/user/netdata/src/web/mcp/bridges/stdio-golang

Your nd-mcp path would be: /home/user/netdata/src/web/mcp/bridges/stdio-golang/nd-mcp

Important: When configuring your AI client, use the full absolute path to the executable:

  • Go bridge: /path/to/bridges/stdio-golang/nd-mcp
  • Node.js bridge: /path/to/bridges/stdio-nodejs/nd-mcp.js
  • Python bridge: /path/to/bridges/stdio-python/nd-mcp.py
Verify the Bridge Works

Once you have nd-mcp (either from existing installation or built), test it:

# Test connection to your Netdata instance (replace YOUR_NETDATA_IP with actual IP)

/path/to/nd-mcp ws://YOUR_NETDATA_IP:19999/mcp

You should see:

nd-mcp: Connecting to ws://YOUR_NETDATA_IP:19999/mcp...

nd-mcp: Connected

Press Ctrl+C to stop the test

Using MCP Remote Client

The official MCP remote client (mcp-remote) is an alternative bridge that enables stdio-only AI clients to connect to Netdata's HTTP and SSE transports (requires Netdata v2.7.2+). Unlike nd-mcp which only supports WebSocket, mcp-remote provides broader transport compatibility.

When to Use MCP Remote

Use mcp-remote when:

  • Your AI client only supports stdio communication
  • You want to use HTTP or SSE transports instead of WebSocket
  • You're running Netdata v2.7.2 or later
  • You don't want to build/install nd-mcp
Installation

No installation required - mcp-remote runs via npx:

# Test the connection

npx mcp-remote@latest --http http://YOUR_NETDATA_IP:19999/mcp \ --allow-http \ --header "Authorization: Bearer YOUR_API_KEY"

Transport Options

mcp-remote supports multiple transport strategies:

# HTTP transport (recommended)

npx mcp-remote@latest --http http://YOUR_NETDATA_IP:19999/mcp \ --allow-http \ --header "Authorization: Bearer YOUR_API_KEY"

SSE transport

npx mcp-remote@latest --sse http://YOUR_NETDATA_IP:19999/mcp \ --allow-http \ --header "Authorization: Bearer YOUR_API_KEY"

Auto-detect with fallback (tries SSE first, falls back to HTTP)

npx mcp-remote@latest --transport sse-first http://YOUR_NETDATA_IP:19999/mcp \ --allow-http \ --header "Authorization: Bearer YOUR_API_KEY"

HTTPS (no --allow-http flag needed)

npx mcp-remote@latest --http https://YOUR_NETDATA_IP:19999/mcp \ --header "Authorization: Bearer YOUR_API_KEY"

Common Options
OptionDescriptionExample
--httpUse HTTP transport--http http://host:19999/mcp
--sseUse SSE transport--sse http://host:19999/mcp
--allow-httpAllow non-HTTPS connections (required for HTTP URLs)--allow-http
--headerAdd custom headers (for authentication)--header "Authorization: Bearer KEY"
--transportTransport strategy--transport sse-first (tries SSE, falls back to HTTP)
--debugEnable debug logging--debug
--hostOAuth callback host (default: localhost)--host 127.0.0.1
Port numberOAuth callback port (optional)9696
Authentication

For Netdata MCP, pass the API key via the Authorization header:

# Using environment variable (recommended)

export NETDATA_MCP_API_KEY="$(cat /var/lib/netdata/mcp_dev_preview_api_key)"

npx mcp-remote@latest --http http://YOUR_NETDATA_IP:19999/mcp \ --allow-http \ --header "Authorization: Bearer $NETDATA_MCP_API_KEY"

Security Note: The --allow-http flag is required for non-HTTPS connections. Only use this on trusted networks as traffic will not be encrypted.

Troubleshooting

Connection Issues:

# Enable debug logging

npx mcp-remote@latest --debug --http http

只显示了开头部分；其余内容请在仓库中阅读

问 PopNx