Manage Your Kubernetes Cluster with k8s mcp-server
Most cloud and infrastructure work still happens through a UI a human drives. Kubernetes MCP server moves it into the conversation instead. Manage Your Kubernetes Cluster with k8s mcp-server.
A Kubernetes Model Context Protocol (MCP) server that provides tools for interacting with Kubernetes clusters through a standardized interface.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 3 tools. What each one is for:
KUBERNETES_CA_CERT — CA certificate content (base64-encoded or PEM format)KUBERNETES_CA_CERT_PATH — Path to CA certificate fileKUBERNETES_INSECURE — Set to "true" to skip TLS verification (not recommended for production)Configuration is passed through the environment: KUBECONFIG_DATA, KUBERNETES_SERVER, KUBERNETES_TOKEN, KUBERNETES_CA_CERT_PATH, KUBECONFIG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
kubectl configured with appropriate cluster accessPlenty 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 — KUBERNETES_CA_CERT, KUBERNETES_CA_CERT_PATH, KUBERNETES_INSECURE — is a fair guide to whether it matches your workflow. It is maintained by reza-gholizade; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| KUBERNETES_CA_CERT | CA certificate content (base64-encoded or PEM format) |
| KUBERNETES_CA_CERT_PATH | Path to CA certificate file |
| KUBERNETES_INSECURE | Set to "true" to skip TLS verification (not recommended for production) |
{
"mcpServers": {
"k8s-mcp-server-reza-gholizade": {
"command": "docker",
"args": ["run", "-i", "--rm", "ginnux/k8s-mcp-server"],
"env": {
"KUBECONFIG_DATA": "your-value",
"KUBERNETES_SERVER": "your-value",
"KUBERNETES_TOKEN": "your-value",
"KUBERNETES_CA_CERT_PATH": "your-value",
"KUBECONFIG": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
kubectl configured with appropriate cluster access| Variable | Description | Required |
|---|---|---|
| KUBECONFIG_DATA | Configuration value read at startup. | Optional |
| KUBERNETES_SERVER | Configuration value read at startup. | Optional |
| KUBERNETES_TOKEN | Credential the server authenticates with. | Yes |
| KUBERNETES_CA_CERT_PATH | Filesystem location the server is allowed to use. | Optional |
| KUBECONFIG | Configuration value read at startup. | Optional |
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.