4,000+ servers built on vurb.ts
Vinkius
Claude DesktopIDE
Netdata MCP Server

Bring Real Time Monitoring
to Claude Desktop

Learn how to connect Netdata to Claude Desktop and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get Agent InfoGet AlarmsGet All MetricsGet Chart DataList ChartsList Room NodesList RoomsList Space AlertsList Space NodesList Spaces

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Netdata

What is the Netdata MCP Server?

Connect your Netdata monitoring infrastructure to any AI agent for instant, real-time observability and performance analysis through natural language.

What you can do

  • Real-time Metrics — Fetch granular data from specific charts (CPU, RAM, Disk, Network) using get_chart_data to diagnose performance bottlenecks.
  • Agent Health — Inspect node versions, host information, and enabled features with get_agent_info and list_charts.
  • Alert Management — Query active alarms on local agents via get_alarms or monitor space-wide critical issues using list_space_alerts.
  • Cloud Orchestration — Navigate your entire infrastructure by listing spaces, rooms, and nodes connected to Netdata Cloud.
  • Scraping & Export — Retrieve all metrics in a format suitable for external analysis tools using get_all_metrics.

How it works

  1. Subscribe to this server
  2. Enter your Netdata Cloud Token or Agent URL
  3. Start monitoring your infrastructure from Claude, Cursor, or any MCP-compatible client

No more jumping between dashboards to find which node is spiking. Your AI acts as a 24/7 SRE or System Administrator.

Who is this for?

  • DevOps Engineers — instantly correlate system alerts with recent deployments without leaving the terminal or IDE.
  • SREs — automate the retrieval of chart data and alarm statuses to speed up incident response.
  • System Administrators — manage large-scale node environments by querying spaces and rooms via simple conversation.

Built-in capabilities (10)

get_agent_info

Get Netdata Agent information

get_alarms

Get current status of all configured alarms

get_all_metrics

Get all metrics for scraping

get_chart_data

Fetch metric data from a specific chart

list_charts

). List all available charts on the node

list_room_nodes

List nodes within a specific room

list_rooms

List rooms within a specific space

list_space_alerts

Fetch active alerts across the space

list_space_nodes

List all nodes connected to a space

list_spaces

List all Netdata Cloud spaces

Why Claude Desktop?

Claude Desktop is the definitive way to connect Netdata to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

  • Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

  • Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

  • Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

  • Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

Netdata in Claude Desktop

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Netdata and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Netdata to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Netdata in Claude Desktop

The Netdata MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Netdata
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Netdata for Claude Desktop

Every tool call from Claude Desktop to the Netdata MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How can I fetch specific metric data for a chart like CPU usage?

Use the get_chart_data tool. You need to provide the chart ID (e.g., 'system.cpu') and optionally specify time ranges like after or aggregation methods like group.

02

Can I see all active alerts across my entire Netdata Cloud space?

Yes! Use the list_space_alerts tool with your space_id. It will return all active alerts across all nodes connected to that specific Cloud space.

03

How do I list all the nodes available in a specific room?

Use the list_room_nodes tool. You will need to provide both the space_id and the room_id to filter the nodes within that specific grouping.

04

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

05

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

06

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

07

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

08

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

09

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

10

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

11

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Explore More MCP Servers

View all →