mcp-server-devops
Fetches dashboard metadata from a Grafana instance via the grafana_dashboard_summary tool, returning a dashboard's title and panel list by UID using a Grafana API key or service account token.
Provides Kubernetes cluster access via the k8s_pod_status tool, listing pod phase, readiness, restart counts, and node placement for a namespace or the whole cluster — using a kubeconfig file or in-cluster service account authentication.
Runs PromQL instant queries against a Prometheus server through the prometheus_query tool, returning raw query results over the HTTP API with optional bearer-token authentication.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-devops are the provisioning-api pods healthy in the prod namespace?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-server-devops
An MCP (Model Context Protocol) server that exposes Kubernetes, Prometheus, and
Grafana observability data as tools an AI assistant (Claude Code, Cursor, Claude Desktop) can call directly during a
conversation — "is this pod healthy", "what's p95 latency on the provisioning API", "summarize the cluster overview
dashboard" — without the human having to switch to kubectl, a PromQL console, or the Grafana UI.
Why this exists
Built after years of running Kubernetes/Prometheus/Grafana observability stacks in production (telecom provisioning platforms, authentication services). The goal is to let an AI coding assistant reason about live system state as part of its context — e.g. "check if the last deploy caused a latency regression before we proceed" — instead of only reasoning about source code.
Related MCP server: Prometheus MCP Server
Tools exposed
Tool | Description |
| Lists pod phase, readiness, restart count, and node for a namespace (or the whole cluster). |
| Runs a PromQL instant query and returns the raw result. |
| Fetches a dashboard's title and panel list by UID. |
Mock mode vs. live mode
Every tool works out of the box with no infrastructure — if the relevant environment variables aren't set, it returns realistic mock data (modeled after a telecom provisioning platform: pods, latency/error-rate metrics, and dashboards). This makes the server demoable and testable without a real cluster.
Set the environment variables below to point a tool at a real backend:
Variable | Tool | Purpose |
|
| Path to a kubeconfig file to query a real cluster. |
|
| Set (any value) to use in-cluster service account auth instead of a kubeconfig. |
|
| Base URL of a Prometheus server, e.g. |
|
| Optional bearer token for authenticated Prometheus instances. |
|
| Base URL of a Grafana instance. |
|
| Grafana API key / service account token. |
Install & build
npm install
npm run buildRun standalone (for debugging)
npm run inspectorThis launches the server behind the official MCP Inspector, a web UI for calling tools manually without needing Claude/Cursor installed.
Register with Claude Code
claude mcp add devops -- node /absolute/path/to/mcp-server-devops/dist/index.jsOr add it to your project's .mcp.json:
{
"mcpServers": {
"devops": {
"command": "node",
"args": ["/absolute/path/to/mcp-server-devops/dist/index.js"],
"env": {
"MCP_PROMETHEUS_URL": "https://prometheus.internal"
}
}
}
}Register with Cursor / Claude Desktop
Add to claude_desktop_config.json (or Cursor's equivalent MCP settings):
{
"mcpServers": {
"devops": {
"command": "node",
"args": ["/absolute/path/to/mcp-server-devops/dist/index.js"]
}
}
}Project layout
src/
index.ts entrypoint: registers tools, starts the stdio transport
tools/k8s.ts Kubernetes pod status (real via @kubernetes/client-node, or mock)
tools/prometheus.ts Prometheus instant query (real via HTTP API, or mock)
tools/grafana.ts Grafana dashboard summary (real via HTTP API, or mock)License
Proprietary — Copyright (c) 2026 Felipe Feres. All Rights Reserved.
This software is proprietary and confidential. No permission is granted to use, copy, modify, or distribute it without the prior express written permission of the owner. See LICENSE for full terms.
Available Tools
3 toolsgrafana_dashboard_summaryGrafana Dashboard SummaryA
Fetch a Grafana dashboard's title and panel list by UID. Connects to a real Grafana instance when MCP_GRAFANA_URL and MCP_GRAFANA_API_KEY are set; otherwise returns mock dashboards ("telecom-provisioning", "k8s-cluster-overview") so the tool is demoable without infra.
Inputs: uid (required).
k8s_pod_statusKubernetes Pod StatusA
List pod status (phase, readiness, restarts, node) for a Kubernetes cluster. Connects to a real cluster when KUBECONFIG or MCP_K8S_IN_CLUSTER is set; otherwise returns realistic mock data for a telecom provisioning platform so the tool is demoable without infra.
Inputs: namespace.
prometheus_queryPrometheus Instant QueryA
Run a PromQL instant query against Prometheus. Connects to a real Prometheus instance when MCP_PROMETHEUS_URL is set (optionally MCP_PROMETHEUS_TOKEN for bearer auth); otherwise returns mock latency/error-rate/resource metrics so the tool is demoable without infra.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
The Polar Signals MCP server enables AI assistants to connect directly with performance profiling data, allowing users to analyze application performance through natural language queries. Key capabilities include querying CPU performance and memory usage, exploring profiling metadata like profile types and labels, and providing AI-driven code optimization suggestions directly within development environments like Claude Code or Cursor.
Query application logs, traces, and metrics from your AI coding assistant via Foam's MCP server.
Query your app's logs, metrics and incidents from your AI assistant.
Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.
Related MCP Servers
- 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
- 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 querying Prometheus metrics, performing cluster diagnostics, and analyzing resource usage through natural language, with automatic Kubernetes connectivity.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query Grafana dashboards, alerts, and datasources for observability insights and incident investigation.MIT