Devops Mcp
Give one agent session unified visibility across Kubernetes, ArgoCD, Prometheus, PagerDuty, and Loki for incident response and deploy checks.
Overview
DevOps MCP is an Operate-phase MCP server that unifies Kubernetes, ArgoCD, Prometheus, PagerDuty, and Loki behind one agent-facing tool surface.
What is this MCP server?
- Single @notharshhaa/devops-mcp v2.1.0 npm stdio server spanning five platforms
- Kubernetes via KUBECONFIG/K8S_CONTEXT; ArgoCD via ARGOCD_SERVER and ARGOCD_TOKEN
- Prometheus queries with PROMETHEUS_URL and optional bearer token
- PagerDuty and Loki integrations for on-call and log correlation during outages
- Package version 2.1.0
- Five integrated platforms: Kubernetes, ArgoCD, Prometheus, PagerDuty, Loki
- Stdio transport via npm identifier @notharshhaa/devops-mcp
Community signal: 1 GitHub stars.
What problem does it solve?
During an outage or deploy, jumping between K8s, GitOps, metrics, paging, and logs wastes minutes you do not have as a solo operator.
Who is it for?
Solo devs and micro-teams on K8s plus Prometheus (optionally ArgoCD, PagerDuty, Loki) who want one MCP for triage.
Skip if: Builders with no cluster yet, Talos-only shops wanting dedicated Talos MCP, or orgs that block agents from production API tokens.
What do I get? / Deliverables
After env vars are set for your stack, the agent can correlate deploy state, cluster health, metrics, incidents, and Loki logs from a single MCP connection.
- One MCP connection covering up to five DevOps backends
- Env-driven configuration for cluster, GitOps, metrics, paging, and logs
- Agent-ready triage workflow without separate CLI hops per system
Recommended MCP Servers
Journey fit
These tools matter once the product is live and you are tracing deploys, metrics, alerts, and logs—not while sketching an MVP UI. Primary shelf is monitoring and observability; ArgoCD ties deploy state into the same incident narrative.
How it compares
Breadth-first observability and GitOps MCP, not a single-purpose label printer or mainframe connector.
Common Questions / FAQ
Who is DevOps MCP for?
It is for indie operators and small teams running Kubernetes-based production with Prometheus and optional ArgoCD, PagerDuty, and Loki who want unified agent access.
When should I use DevOps MCP?
Use it in Operate when debugging incidents, validating rollouts, or answering what changed across cluster, GitOps, metrics, alerts, and logs.
How do I add DevOps MCP to my agent?
Add @notharshhaa/devops-mcp v2.1.0 as a stdio MCP server in Claude Code or Cursor and set KUBECONFIG plus PROMETHEUS_URL and any of ARGOCD_*, PAGERDUTY_TOKEN, and Loki-related vars your install requires.