Compatible with every major AI agent and IDE
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_datato diagnose performance bottlenecks. - Agent Health — Inspect node versions, host information, and enabled features with
get_agent_infoandlist_charts. - Alert Management — Query active alarms on local agents via
get_alarmsor monitor space-wide critical issues usinglist_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
- Subscribe to this server
- Enter your Netdata Cloud Token or Agent URL
- 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 Netdata Agent information
Get current status of all configured alarms
Get all metrics for scraping
Fetch metric data from a specific chart
). List all available charts on the node
List nodes within a specific room
List rooms within a specific space
Fetch active alerts across the space
List all nodes connected to a space
List all Netdata Cloud spaces
Why Cursor?
Cursor's Agent mode turns Netdata into an in-editor superpower. Ask Cursor to generate code using live data from Netdata and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Netdata in Cursor
Netdata and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Netdata to Cursor 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Netdata in Cursor
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 Cursor 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.

* 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
How Vinkius secures
Netdata for Cursor
Every tool call from Cursor to the Netdata MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
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.
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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Xata
28 toolsAutomate your serverless database workflows with Xata — manage organizations, projects, and branches directly from your AI agent.

Coalesce
8 toolsEnable your AI agent to manage Snowflake data pipelines, trigger transformations, and monitor jobs via the Coalesce API.

Quantive (Gtmhub)
10 toolsAutomate OKR strategy via Quantive — manage objectives, key results, and sessions directly from any AI agent.

Deck Commerce
10 toolsEquip your AI agent to manage order fulfillment, track shipments, and monitor inventory via the Deck Commerce API.
