#Kubernetes MCP Servers

Deploy and manage cloud infrastructure with simple virtual servers, managed databases, and Kubernetes clusters built for developers.

Manage Kubernetes deployments via Argo CD. Sync applications, check logs, and manage clusters/repositories directly from your AI agent.

Manage Linode cloud infrastructure. Provision compute instances, manage Kubernetes clusters (LKE), and monitor account details directly from your AI agent.

Automate Kubernetes orchestrations via Argo Workflows. Monitor, list, and inspect active pods, crons, and workflow templates directly from any AI agent.

Orchestrate Kubernetes clusters via Porter. Manage apps, projects, container tags, and enforce rollouts directly with your AI.

Equip your AI to manage Kubernetes environments directly through Rancher, overseeing clusters, namespaces, and active pods.

Monitor and analyze Kubernetes infrastructure costs. Query workload allocations, backing assets, and cloud billing directly from your AI agent.

Manage Docker containers and environments via Portainer. List, create, and start containers directly from your AI agent.

Manage CI/CD and GitOps via Codefresh. Track pipelines, trigger builds, and monitor delivery clusters directly from any AI agent.

Bring effortless Kubernetes and cloud deployment management to your IDE. List environments, check application states, restart pods, and deploy exact Git commits via chat.

Cloud-native API Management & Gateway evaluating proxy topologies explicitly running Kubernetes integrations.

Manage Civo cloud infrastructure. Provision Kubernetes clusters, control compute instances, and monitor usage directly via AI.

Manage high-performance AI infrastructure on CoreWeave. Provision GPU clusters, configure VPCs, and orchestrate inference gateways directly from your AI agent.

An AI generated Kubernetes manifests for a payment service. No resource requests or limits. No PodSecurityStandards. Single replica, no PDB. Zero NetworkPolicies. Every pod could reach every other pod. The payment pod got OOM-killed at 3 AM by a logging sidecar with no memory ceiling. This tool forces resource governance, security hardening, reliability design, observability instrumentation, and network restriction on every workload.