| 1 | # MCP Clients |
| 2 | |
| 3 | Model Context Protocol (MCP) clients like **Claude Desktop**, **Cursor**, **Visual Studio Code**, **JetBrains IDEs**, **Netdata Web Client**, **Claude Code**, and **Gemini CLI** can connect to Netdata’s MCP server to bring real observability data into your AI workflows. This enables natural‑language analysis with context from your infrastructure and, for CLI tools, optional automation. |
| 4 | |
| 5 | ## The power of MCP clients |
| 6 | |
| 7 | ### Key Capabilities |
| 8 | |
| 9 | **Observability‑driven operations** |
| 10 | |
| 11 | - Access real-time metrics and logs from monitoring systems |
| 12 | - Analyze performance trends and identify bottlenecks |
| 13 | - Correlate issues across multiple systems and services |
| 14 | |
| 15 | **System configuration management** |
| 16 | |
| 17 | - Generate and modify configuration files based on observed conditions |
| 18 | - Implement best practices automatically |
| 19 | - Adapt configurations to changing requirements |
| 20 | |
| 21 | **Automated troubleshooting** |
| 22 | |
| 23 | - Diagnose issues using multiple data sources |
| 24 | - Execute diagnostic commands and interpret results |
| 25 | - Implement fixes based on root cause analysis |
| 26 | |
| 27 | ## Observability + automation use cases |
| 28 | |
| 29 | When MCP clients have access to Netdata, they can make informed decisions about system changes: |
| 30 | |
| 31 | ### Infrastructure Optimization Examples |
| 32 | |
| 33 | **Database Performance Tuning:** |
| 34 | |
| 35 | ``` |
| 36 | PostgreSQL is showing high query response times. Check the metrics and optimize |
| 37 | the configuration. |
| 38 | ``` |
| 39 | |
| 40 | The AI analyzes connection counts, query performance, and resource usage to adjust connection pools, memory settings, and query optimization parameters. |
| 41 | |
| 42 | **Resource Management:** |
| 43 | |
| 44 | ``` |
| 45 | This Kubernetes cluster is experiencing frequent pod restarts. Investigate and |
| 46 | fix the resource allocation. |
| 47 | ``` |
| 48 | |
| 49 | The AI examines CPU, memory, and network metrics to identify resource constraints and adjust limits, requests, and HPA configurations. |
| 50 | |
| 51 | **Storage Optimization:** |
| 52 | |
| 53 | ``` |
| 54 | Disk usage is growing rapidly on our log servers. Implement appropriate |
| 55 | retention policies. |
| 56 | ``` |
| 57 | |
| 58 | The AI analyzes disk growth patterns, identifies log volume trends, and configures rotation, compression, and cleanup policies. |
| 59 | |
| 60 | **Network Performance:** |
| 61 | |
| 62 | ``` |
| 63 | API response times are inconsistent. Check network metrics and optimize the |
| 64 | load balancer configuration. |
| 65 | ``` |
| 66 | |
| 67 | The AI examines network latency, connection distribution, and backend health to adjust load balancing algorithms and connection settings. |
| 68 | |
| 69 | **Monitoring Setup:** |
| 70 | |
| 71 | ``` |
| 72 | This server runs Redis but we're not monitoring it properly. Please configure |
| 73 | comprehensive monitoring. |
| 74 | ``` |
| 75 | |
| 76 | The AI detects the Redis installation, configures appropriate collectors, sets up alerting thresholds, and verifies metric collection. |
| 77 | |
| 78 | **Auto-scaling Configuration:** |
| 79 | |
| 80 | ``` |
| 81 | Set up intelligent auto-scaling based on current usage patterns I'm seeing. |
| 82 | ``` |
| 83 | |
| 84 | The AI analyzes historical resource utilization to configure scaling policies, thresholds, and cooldown periods that match actual workload patterns. |
| 85 | |
| 86 | **Complex Test Environment Setup:** |
| 87 | |
| 88 | ``` |
| 89 | I need a complete test environment that mirrors our production setup: a |
| 90 | multi-tier application with PostgreSQL primary/replica, Redis cluster, message |
| 91 | queues, and load balancers. Set up everything with a Netdata monitoring |
| 92 | everything and realistic test data. |
| 93 | ``` |
| 94 | |
| 95 | The AI leverages its deep knowledge of application architectures and Netdata's monitoring capabilities to: |
| 96 | |
| 97 | - Deploy and configure all required services with production-like settings |
| 98 | - Set up database replication, clustering, and connection pooling |
| 99 | - Configure realistic test datasets and user simulation |
| 100 | - Implement comprehensive monitoring for all components with appropriate alerts |
| 101 | - Create load testing scenarios that match production traffic patterns |
| 102 | - Establish proper network segmentation and security configurations |
| 103 | - Generate documentation for the test environment and runbooks for common scenarios |
| 104 | |
| 105 | Keep in mind however, that usually this prompt should be split into multiple smaller prompts, so that the LLM can focus on completing a smaller task at a time. |
| 106 | |
| 107 | This showcases how AI can combine application expertise, infrastructure knowledge, and observability best practices to create sophisticated testing environments that would typically require weeks of manual setup and deep domain expertise. |
| 108 | |
| 109 | ## ⚠️ Critical security and safety considerations |
| 110 | |
| 111 | ### Command execution risks |
| 112 | |
| 113 | **LLMs Are Not Infallible:** |
| 114 | |
| 115 | - AI assistants can misinterpret requirements or generate incorrect commands |
| 116 | - Complex system interactions may not be fully understood by the model |
| 117 | - Edge cases and system-specific configurations can lead to unexpected results |
| 118 | |
| 119 | **System Impact Awareness:** |
| 120 | |
| 121 | - Commands can affect system stability, performance, and security |
| 122 | - Changes may have cascading effects across interconnected services |
| 123 | - Recovery from AI-generated misconfigurations can be time-consuming |
| 124 | |
| 125 | ### Data privacy and security concerns |
| 126 | |
| 127 | **External LLM Provider Exposure:** |
| 128 | |
| 129 | - All data accessed by the AI (files, configurations, command outputs) is transmitted to external providers |
| 130 | - Sensitive information like passwords, API keys, certificates, and secrets may be inadvertently exposed |
| 131 | - Infrastructure topology, performance metrics, and operational details become visible to third parties |
| 132 | - Compliance requirements (GDPR, HIPAA, SOX) may be violated by external data transmission |
| 133 | |
| 134 | **Network and System Information:** |
| 135 | |
| 136 | - Database connection strings and credentials |
| 137 | - Network topology and security configurations |
| 138 | - Application secrets and encryption keys |
| 139 | - User data and personally identifiable information |
| 140 | |
| 141 | ### Recommended safe usage practices |
| 142 | |
| 143 | **1. Analysis-First Approach:** |
| 144 | |
| 145 | ``` |
| 146 | Instead of: Fix the high CPU usage on server X |
| 147 | Try: Analyze the CPU metrics on server X and explain what might be causing |
| 148 | high usage and what solutions you recommend |
| 149 | ``` |
| 150 | |
| 151 | **2. Review and Validation:** |
| 152 | |
| 153 | - Always review AI-generated commands before execution |
| 154 | - Test suggestions in development environments first |
| 155 | - Understand the impact and side effects of proposed changes |
| 156 | - Have rollback procedures ready |
| 157 | |
| 158 | **3. Data Sanitization:** |
| 159 | |
| 160 | - Remove or mask sensitive information before sharing with AI |
| 161 | - Use environment variables or placeholder values for secrets |
| 162 | - Avoid sharing production credentials or keys |
| 163 | - Consider using development/staging data for analysis |
| 164 | |
| 165 | **4. Graduated Permissions:** |
| 166 | |
| 167 | - Start with read-only access for analysis |
| 168 | - Grant execution permissions gradually based on trust and validation |
| 169 | - Use separate accounts with limited privileges for AI operations |
| 170 | - Implement audit logging for all AI-initiated changes |
| 171 | |
| 172 | **5. Environment Separation:** |
| 173 | |
| 174 | - Use AI assistance primarily in development and testing environments |
| 175 | - Require manual approval for production changes |
| 176 | - Implement change management processes for AI-suggested modifications |
| 177 | - Maintain air-gapped environments for highly sensitive systems |
| 178 | |
| 179 | ## Best practices for implementation |
| 180 | |
| 181 | ### Safe integration workflow |
| 182 | |
| 183 | 1. **Discovery Phase:** Let AI analyze your current setup and identify opportunities |
| 184 | 2. **Planning Phase:** Have AI generate detailed implementation plans with explanations |
| 185 | 3. **Review Phase:** Manually review all suggested changes and commands |
| 186 | 4. **Testing Phase:** Implement changes in non-production environments |
| 187 | 5. **Validation Phase:** Verify results match expectations before production deployment |
| 188 | 6. **Documentation Phase:** Have AI help document the changes and their rationale |
| 189 | |
| 190 | ### Building trust over time |
| 191 | |
| 192 | - Start with simple, low-risk tasks to build confidence |
| 193 | - Gradually increase complexity as you validate AI accuracy |
| 194 | - Develop institutional knowledge about AI strengths and limitations |
| 195 | - Create feedback loops to improve AI prompts and instructions |
| 196 | |
| 197 | ### Team education and guidelines |
| 198 | |
| 199 | ## Client guides |
| 200 | |
| 201 | See dedicated configuration guides for each client: |
| 202 | |
| 203 | - Claude Desktop |
| 204 | - Cursor |
| 205 | - Visual Studio Code |
| 206 | - JetBrains IDEs |
| 207 | - Netdata Web Client |
| 208 | - Claude Code |
| 209 | - Gemini CLI |
| 210 | |
| 211 | - Train team members on safe AI usage practices |
| 212 | - Establish clear guidelines for when AI assistance is appropriate |
| 213 | - Create approval processes for AI-suggested changes |
| 214 | - Share lessons learned and best practices across teams |
| 215 | |
| 216 | ## The Future of AI-Driven Operations |
| 217 | |
| 218 | CLI-based AI assistants represent the beginning of a transformation in infrastructure management. As these tools mature, they will likely become central to: |
| 219 | |
| 220 | - **Predictive Operations:** Proactively identifying and preventing issues before they occur |
| 221 | - **Adaptive Infrastructure:** Systems that automatically optimize themselves based on changing conditions |
| 222 | - **Intelligent Automation:** Context-aware automation that understands business impact |
| 223 | - **Enhanced Collaboration:** AI as a knowledgeable team member that augments human expertise |
| 224 | |
| 225 | However, the human element remains crucial for oversight, validation, and strategic decision-making. The most successful implementations will be those that thoughtfully balance AI capabilities with human judgment and appropriate safety measures. |