Integration

Netdata integration

Netdata is a self-hosted real-time infrastructure monitoring agent that collects per-second metrics, health alerts and machine-learning anomaly scores from servers, containers and applications. Query time-series data across one node or a whole parent/child streaming cluster, list nodes, node instances, contexts and charts, run full-text search over metric names and labels, score which metrics changed most during an incident, read raised and cleared alerts with their transition history and configuration, inspect and run collector functions such as processes, systemd services, network connections and log tailing, read and write dynamic collector configuration and user settings, follow the progress of a long query, read agent, streaming and database-engine status, read the machine-learning model state, and render a chart value as an SVG badge. This file targets the AGENT API (v3 for everything it covers, v1 for the chart, alarm, correlation and internals routes that have no v3 equivalent), not Netdata Cloud. The host is part of the credential because every install is its own deployment. Authentication is a bearer token, required only when bearer protection is enabled on the agent.

Connect Netdata How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Netdata.Built from the 37 Netdata tools below, on the connection you add once.

What you can do with Netdata

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Function, 3 operations

list_functionsList functionsGETList available functions across all nodes.
run_functionRun functionGETExecute a Netdata function on a specific node.
run_function_with_payloadRun function with payloadPOSTExecute a Netdata function with request body parameters.

Chart, 2 operations

get_chartGet chartGETGet one chart v1 - EOL.
list_chartsList chartsGETList all charts v1 - EOL.

Config, 2 operations

get_dynamic_configGet dynamic configGETManage Netdata dynamic configuration.
update_dynamic_configUpdate dynamic configPOSTManage Netdata configuration with request body data.

Context, 2 operations

get_contextGet contextGETGet info about a specific context - Latest API.
list_contextsList contextsGETContexts Info v3.

Setting, 2 operations

get_user_settingsGet user settingsGETRetrieve user settings/preferences (GET).
replace_user_settingsReplace user settingsPUTCreate or update user settings/preferences (PUT).

Aclk, 1 operation

get_cloud_link_statusGet cloud link statusGETGet information about current ACLK state.

Alarm, 1 operation

list_raised_alarmsList raised alarmsGETGet a list of active or raised alarms on the server.

Alarm count, 1 operation

count_alarmsCount alarmsGETGet an overall status of the chart.

Alarm log, 1 operation

list_alarm_logList alarm logGETRetrieves the entries of the alarm log.

Alarm variable, 1 operation

list_alarm_variablesList alarm variablesGETList variables available to configure alarms for a chart.

Alarms value, 1 operation

list_alarm_valuesList alarm valuesGETGet a list of active or raised alarms on the server.

Alert, 1 operation

list_alertsList alertsGETCurrent Alert Status - Multi-node Alert Information - Latest API.

Alert config, 1 operation

get_alert_configGet alert configGETRetrieve the configuration of a specific alert by its config hash ID.

Alert transition, 1 operation

list_alert_transitionsList alert transitionsGETRetrieve alert state transition history across all nodes with advanced filtering.

Badge svg, 1 operation

render_metric_badgeRender metric badgeGETGenerate a badge in form of SVG image for a chart (or dimension) - Latest API.

Claim, 1 operation

get_cloud_claim_statusGet cloud claim statusGETClaim agent to Netdata Cloud.

Data, 1 operation

query_metric_dataQuery metric dataGETData Query v3.

Dbengine stat, 1 operation

get_dbengine_statsGet dbengine statsGET[DEPRECATED] Get DBEngine storage statistics.

Info, 1 operation

get_agent_infoGet agent infoGETRetrieve detailed Netdata agent information across all nodes.

Me, 1 operation

get_current_userGet current userGETGet current authenticated user information.

Metric correlation, 1 operation

find_metric_correlationsFind metric correlationsGETAnalyze all the metrics to find their correlations - EOL.

Ml info, 1 operation

get_machine_learning_infoGet machine learning infoGET[DEPRECATED] Get machine learning detection information.

Node, 1 operation

list_nodesList nodesGETNodes Info v3.

Node instance, 1 operation

list_node_instancesList node instancesGETRetrieve chart instances organized by node across the infrastructure.

Progres, 1 operation

get_query_progressGet query progressGETTrack progress of long-running function executions.

Q, 1 operation

search_metricsSearch metricsGETFull Text Search v3.

Stream info, 1 operation

get_streaming_infoGet streaming infoGETGet streaming information and statistics.

Stream path, 1 operation

get_streaming_pathGet streaming pathGETRetrieve streaming topology path for nodes.

Variable, 1 operation

get_chart_variableGet chart variableGETRetrieve the value of a specific chart variable used in alert expressions.

Version, 1 operation

get_versionsGet versionsGETRetrieve Netdata agent version information across nodes.

Weight, 1 operation

score_metric_weightsScore metric weightsGETScore or weight all or some of the metrics, across all nodes, according to various algorithms.

Use Netdata from Claude Code, Cursor or Codex

Connect Netdata in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Netdata operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Netdata

Create your workspace
Sign up free. Nothing to install.
Connect Netdata once
Add your Netdata connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.