Best MCP servers for Kubernetes and containers
Operating containers means constantly answering small, urgent questions: which pods are crash-looping, what do the logs say, is this deployment synced, what is running on the cluster right now. An agent with direct access to the orchestration layer can list resources, read logs, and explain failures in plain language, far faster than chaining kubectl and docker commands by hand. The right server depends on where you sit, a native Kubernetes API client for cluster operations, a container gateway for running and aggregating workloads, or a GitOps controller for reconciling declared state against what is actually deployed. The servers below cover the common container surface, each a real MCP server with a verified, current install config.
Kubernetes
containers (Red Hat)
Native Kubernetes and OpenShift MCP server: list, inspect, and manage cluster resources, pods, and Helm releases directly through the Kubernetes API.
A native Kubernetes and OpenShift server lists, inspects, and manages cluster resources, pods, and Helm releases through the Kubernetes API, the core tool for cluster operations.
Docker
Docker
Docker's official MCP Gateway: run, secure, and aggregate containerized MCP servers behind one endpoint, with on-demand discovery from the Docker MCP Catalog.
Docker's official MCP Gateway runs, secures, and aggregates containerized MCP servers behind one endpoint with on-demand discovery, the container-runtime entry point.
Argo CD
Argo Project (argoproj-labs)
The Argo CD MCP server lets an agent inspect and manage GitOps applications — list and sync apps, read resource trees and workload logs, and run resource act...
The Argo CD server inspects and manages GitOps applications, listing and syncing apps, reading resource trees and workload logs, and running resource actions, ideal for declarative deployment workflows.