Kubernetes 🚀 MCP Server

MCP Server that talks to the Kubernetes APIs

Local serverstdioGo

What is the Kubernetes 🚀 MCP server?

Most cloud and infrastructure work still happens through a UI a human drives. Kubernetes 🚀 MCP server moves it into the conversation instead. MCP Server that talks to the Kubernetes APIs.

The short version

The Kubernetes MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with Kubernetes APIs, enabling advanced automation and interaction capabilities for developers, operators, and AI tools.

This MCP server enables AI tools to interact with Kubernetes clusters using natural language, providing capabilities to:

The tools it exposes

The server publishes 1 tool. What each one is for:

  • stdio — The stdio transport is the default and recommended option for most users for local integration:

What it needs from you

Configuration is passed through the environment: K8S_MCP_TOOLSETS. 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.

  1. A Kubernetes cluster with API access 2. Valid kubeconfig file or service account credentials 3. Appropriate RBAC permissions for desired operations

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

How it compares

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Kubernetes 🚀's toolset — stdio — is a fair guide to whether it matches your workflow. It is maintained by briankscheong; 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.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
stdioThe stdio transport is the default and recommended option for most users for local integration:

How to install the Kubernetes 🚀 MCP server

{
  "mcpServers": {
    "kubernetes": {
      "command": "path/to/k8smcp",
      "args": [
        "stdio",
        "--kubeconfig=/path/to/your/kubeconfig"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  1. A Kubernetes cluster with API access 2. Valid kubeconfig file or service account credentials 3. Appropriate RBAC permissions for desired operations
VariableDescriptionRequired
K8S_MCP_TOOLSETSConfiguration value read at startup.Optional

Example prompts to try

  • Use Kubernetes 🚀 to stdio.

Frequently asked questions

It supports `stdio` (default, for local integration) and `sse` (HTTP-based JSON-RPC, for deploying inside a Kubernetes cluster).