Model Context Protocol (MCP) server for Kubernetes and OpenShift
If you already use Kubernetes, the kubernetes mcp server is the piece that lets your assistant work with it directly. Model Context Protocol (MCP) server for Kubernetes and OpenShift.
A powerful and flexible Kubernetes Model Context Protocol (MCP) server implementation with support for Kubernetes and OpenShift.
args on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
configuration_contexts_list — List all available context names and associated server urls from the kubeconfig filetargets_list — List all available targetsconfiguration_view — Get the current Kubernetes configuration content as a kubeconfig YAMLevents_list — List Kubernetes events (warnings, errors, state changes) for debugging and troubleshooting in the current cluster from all namespacesnamespaces_list — List all the Kubernetes namespaces in the current clusterprojects_list — List all the OpenShift projects in the current clusternodes_log — Get logs from a Kubernetes node (kubelet, kube-proxy, or other system logs). This accesses node logs through the Kubernetes API proxy to the kubeletnodes_stats_summary — Get detailed resource usage statistics from a Kubernetes node via the kubelet's Summary API. Provides comprehensive metrics including CPU, memorynodes_top — List the resource consumption (CPU and memory) as recorded by the Kubernetes Metrics Server for the specified Kubernetes Nodes or all nodes in theToolset — Descriptionconfig — View and manage the current local Kubernetes configuration (kubeconfig)core — Most common tools for Kubernetes management (Pods, Generic Resources, Events, etc.)Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Kubernetes's toolset — configuration_contexts_list, targets_list, configuration_view and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| configuration_contexts_list | List all available context names and associated server urls from the kubeconfig file |
| targets_list | List all available targets |
| configuration_view | Get the current Kubernetes configuration content as a kubeconfig YAML |
| events_list | List Kubernetes events (warnings, errors, state changes) for debugging and troubleshooting in the current cluster from all namespaces |
| namespaces_list | List all the Kubernetes namespaces in the current cluster |
| projects_list | List all the OpenShift projects in the current cluster |
| nodes_log | Get logs from a Kubernetes node (kubelet, kube-proxy, or other system logs). This accesses node logs through the Kubernetes API proxy to the kubelet |
| nodes_stats_summary | Get detailed resource usage statistics from a Kubernetes node via the kubelet's Summary API. Provides comprehensive metrics including CPU, memory, filesystem, and network usage at the node, pod, and container levels. On |
| nodes_top | List the resource consumption (CPU and memory) as recorded by the Kubernetes Metrics Server for the specified Kubernetes Nodes or all nodes in the cluster |
| Toolset | Description |
| config | View and manage the current local Kubernetes configuration (kubeconfig) |
| core | Most common tools for Kubernetes management (Pods, Generic Resources, Events, etc.) |
| helm | Tools for managing Helm charts and releases |
| kcp | Manage kcp workspaces and multi-tenancy features |
{
"mcpServers": {
"kubernetes": {
"command": "npx",
"args": ["-y", "kubernetes-mcp-server@latest"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.