mcp-server-devops
Related Servers
Alternatives to mcp-server-devops
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to query Grafana datasources (Prometheus/Loki metrics and SQL databases like ClickHouse/Postgres/MySQL) and search or inspect dashboards through natural language, using read-only access to Grafana's API.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query Prometheus metrics, monitor alerts, and analyze system health through read-only access to your Prometheus server with built-in query safety and optional AI-powered metric analysis.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query Grafana dashboards, alerts, and datasources for observability insights and incident investigation.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read Grafana dashboards, alert rules, and query datasources (Prometheus, Loki, etc.) through MCP tools, integrating Grafana monitoring into the IDE.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying Prometheus metrics, performing cluster diagnostics, and analyzing resource usage through natural language, with automatic Kubernetes connectivity.MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with Grafana dashboards, datasources, alerts, incidents, and monitoring data through 43 comprehensive tools. Supports querying Prometheus metrics, Loki logs, managing incidents, and dashboard operations with full authentication support.43694 npm3MIT
TDQS
Scored across 3 tools
Each tool targets a clearly distinct system and data type: Kubernetes pod status, Prometheus metrics, and Grafana dashboards. There is no realistic scenario where an agent would confuse one for another.
All names are snake_case and include a product/resource prefix, but the patterns vary slightly: k8s_pod_status and grafana_dashboard_summary are noun phrases while prometheus_query uses a product_action form. The deviation is minor and still highly readable.
Three tools is technically within the reasonable 3-15 range, but for a server labeled 'devops' the surface feels thin and narrow, covering only observability reads. More operational breadth would justify the server name better.
The surface is limited to read-only observability: pod status, a PromQL query, and a dashboard summary. There are significant gaps for a DevOps server, including logs, deployments, services, events, alerting, and any write or remediation operations.