k8s

This MCP server provides a standardized interface for interacting with Kubernetes clusters. It exposes capabilities such as API resource discovery, resource listing and details, resource creation or updates from YAML/JSON manifests, deletions, and observability features like pod logs and node/pod metrics. The server supports multiple transport modes via MCP: stdio for CLI integrations, SSE for web applications, and streamable-http for web clients, with an optional read-only mode to prevent writes. To get started, run the server in one of the supported modes and point it at your Kubernetes cluster using one of the authentication methods described in the deployment guide. Once running, you can query resources, watch events, fetch logs, and manage resources through the MCP interface in a consistent manner across modes.

Prerequisites:

• Go 1.23 or later
• Access to a Kubernetes cluster
• kubectl configured with appropriate cluster access

Installation steps:

1. Clone the repository

git clone https://github.com/reza-gholizade/k8s-mcp-server.git
cd k8s-mcp-server

2. Install dependencies

go mod download

3. Build the server

go build -o k8s-mcp-server main.go

4. Run the server (example)

./k8s-mcp-server --mode sse --port 8080

Optional: set environment variables to configure authentication and modes, for example:

export SERVER_MODE=sse
export SERVER_PORT=8080
export KUBECONFIG_DATA="$(cat ~/.kube/config)"
./k8s-mcp-server

Tips and notes:

• The server supports multiple authentication methods with a priority order: kubeconfig data, API server URL + token, in-cluster service account, and kubeconfig file path. If you deploy inside Kubernetes, prefer the in-cluster ServiceAccount approach for seamless access.
• In read-only mode, createResource and related Helm management operations are disabled. Use this for safe exploration.
• If you encounter TLS issues, you can provide KUBERNETES_CA_CERT_PATH or set KUBERNETES_INSECURE=true for testing, but avoid insecure settings in production.
• Ensure the service account (if used) has the necessary RBAC permissions for the resources you plan to manage (get/list/watch/create/update/patch/delete).
• The server can operate in stdio, SSE, or streamable-http modes; pick the mode that best fits your integration (CLI tools vs web apps).
• When wiring to Kubernetes clusters with restricted networks, ensure API server accessibility from the MCP server host and proper network policies.