MCP K8s

What silenceper/mcp-k8s MCP server does

The silenceper/mcp-k8s MCP server connects an MCP client to a Kubernetes cluster and exposes tools for resource discovery, resource operations, and Helm management. It supports built-in Kubernetes resources and custom resources defined through CRDs.

Resource tools can retrieve details for a specific object, list objects of a given type with filtering options, and create, update, or delete resources. The server also provides Helm tools for inspecting releases, installing or upgrading charts, removing releases, and managing Helm repositories.

Write operations are configurable. Create, update, and delete actions can each be enabled or disabled separately. Helm installation, upgrade, uninstall, repository addition, and repository removal also have independent controls.

How it works

The server is written in Go and uses the mcp-go SDK for MCP communication. Kubernetes access is provided through the client-go library, while Helm actions use the Helm v3 client library. Cluster credentials and connection details come from a kubeconfig file.

By default, the server communicates over standard input and output, which suits local MCP clients. It can also expose an HTTP endpoint using either Server-Sent Events or Streamable HTTP. SSE uses the /sse endpoint, while Streamable HTTP uses /mcp by default, with the host, port, and endpoint path configurable through command-line flags.

Setup and configuration

You can download a platform-specific binary from the project's releases, install it with Go, or build it from source using the repository's Makefile. The Go installation command is:

go install github.com/silenceper/mcp-k8s/cmd/mcp-k8s@latest

A local stdio configuration points the MCP client at the compiled mcp-k8s executable and passes the kubeconfig path as --kubeconfig. Additional flags such as --enable-create, --enable-update, --enable-delete, and --enable-list control resource operations. Helm permissions use flags including --enable-helm-install and --enable-helm-upgrade.

Docker images are published at ghcr.io/silenceper/mcp-k8s:latest. The documented container setup mounts a kubeconfig file at /root/.kube/config and can run in stdio, SSE, or Streamable HTTP mode.

Tools and capabilities

The available tools include:

• get_api_resources for discovering supported API resource types
• get_resource and list_resources for reading Kubernetes objects
• create_resource, update_resource, and delete_resource for mutations
• list_helm_releases and get_helm_release for release inspection
• install_helm_chart, upgrade_helm_chart, and uninstall_helm_chart for release actions
• list_helm_repositories, add_helm_repository, and remove_helm_repository for repository management

These capabilities support cluster status checks, configuration work, test-environment management, and operator workflows where an LLM translates requests into Kubernetes actions.

Limitations and notes

The server requires access to a kubeconfig and the corresponding Kubernetes permissions. Enabling mutation or Helm tools allows the connected MCP client to perform changes, so operation flags should be selected according to the intended access level. The README specifically notes that remotely deployed SSE mode requires attention to security. The provided material does not describe authentication for the HTTP endpoints, access-control behavior beyond operation flags, or a hosted service.

The silenceper/mcp-k8s MCP server is an interface to Kubernetes and Helm; it does not replace cluster authorization or the underlying permissions configured for the supplied kubeconfig.