# Netdata MCP server

> Query real-time metrics, logs, alerts and ML anomaly detection from your Netdata-monitored infrastructure.

- Listing: https://mcp.tc/i/netdata
- Connect: use the server's own URL `https://app.netdata.cloud/api/v1/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Observability & Incidents](https://mcp.tc/c/observability)
- Vendor: Netdata
- Homepage: <https://www.netdata.cloud>
- Repository: <https://github.com/netdata/netdata>

## About

Connects an assistant to Netdata Cloud, which aggregates data from Netdata Agents running on servers, containers, Kubernetes and applications. It exposes per-second metrics, logs, alerts and machine-learning anomaly detection so the assistant can help investigate problems across monitored nodes.

The server is hosted at app.netdata.cloud over streamable HTTP. It requires a Netdata Cloud API token with the mcp scope, sent as a bearer token in the Authorization header. Each Netdata Agent can also serve MCP locally.

## What it can do

- Query real-time infrastructure metrics from monitored nodes
- Read logs from monitored systems
- Check active and past alerts
- Use ML-based anomaly detection to find unusual behavior
- Troubleshoot issues across servers, containers and applications

## Example prompts

- "Which of my nodes have critical alerts right now?"
- "Show CPU and memory trends on my database server over the last hour."
- "Were there any anomalies on my web nodes since yesterday?"
- "Find the likely cause of the latency spike at 14:00."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http netdata https://app.netdata.cloud/api/v1/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
```

2. Replace the placeholder with your key before you run it, then check it with `/mcp` inside Claude Code.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Custom connectors can’t send this server’s key header, so use the `mcp-remote` bridge. Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "netdata": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.netdata.cloud/api/v1/mcp",
        "--header",
        "Authorization: Bearer <YOUR_API_KEY>"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=netdata&config=eyJ1cmwiOiJodHRwczovL2FwcC5uZXRkYXRhLmNsb3VkL2FwaS92MS9tY3AiLCJoZWFkZXJzIjp7IkF1dGhvcml6YXRpb24iOiJCZWFyZXIgPFlPVVJfQVBJX0tFWT4ifX0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "netdata": {
      "url": "https://app.netdata.cloud/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the key the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "netdata": {
      "type": "http",
      "url": "https://app.netdata.cloud/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${input:api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "api-key",
      "description": "API key",
      "password": true
    }
  ]
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "netdata": {
      "serverUrl": "https://app.netdata.cloud/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add netdata --url https://app.netdata.cloud/api/v1/mcp --bearer-token-env-var NETDATA_API_KEY
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.netdata]
url = "https://app.netdata.cloud/api/v1/mcp"
bearer_token_env_var = "NETDATA_API_KEY"
```

Set `NETDATA_API_KEY` to your key in the shell that runs Codex.

### Gemini CLI

```bash
gemini mcp add --transport http --header "Authorization: Bearer <YOUR_API_KEY>" netdata https://app.netdata.cloud/api/v1/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "netdata": {
      "type": "http",
      "url": "https://app.netdata.cloud/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://app.netdata.cloud/api/v1/mcp`.

## Details

- Server version: 2.12.0
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/netdata (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report