base on Model Context Protocol (MCP) server for Kubernetes and OpenShift # Kubernetes MCP Server [](https://github.com/manusa/kubernetes-mcp-server/blob/main/LICENSE) [](https://www.npmjs.com/package/kubernetes-mcp-server) [](https://pypi.org/project/kubernetes-mcp-server/) [](https://github.com/manusa/kubernetes-mcp-server/releases/latest) [](https://github.com/manusa/kubernetes-mcp-server/actions/workflows/build.yaml) [✨ Features](#features) | [🚀 Getting Started](#getting-started) | [🎥 Demos](#demos) | [⚙️ Configuration](#configuration) | [🛠️ Tools](#tools) | [🧑‍💻 Development](#development) https://github.com/user-attachments/assets/be2b67b3-fc1c-4d11-ae46-93deba8ed98e ## ✨ Features <a id="features"></a> A powerful and flexible Kubernetes [Model Context Protocol (MCP)](https://blog.marcnuri.com/model-context-protocol-mcp-introduction) server implementation with support for **Kubernetes** and **OpenShift**. - **✅ Configuration**: - Automatically detect changes in the Kubernetes configuration and update the MCP server. - **View** and manage the current [Kubernetes `.kube/config`](https://blog.marcnuri.com/where-is-my-default-kubeconfig-file) or in-cluster configuration. - **✅ Generic Kubernetes Resources**: Perform operations on **any** Kubernetes or OpenShift resource. - Any CRUD operation (Create or Update, Get, List, Delete). - **✅ Pods**: Perform Pod-specific operations. - **List** pods in all namespaces or in a specific namespace. - **Get** a pod by name from the specified namespace. - **Delete** a pod by name from the specified namespace. - **Show logs** for a pod by name from the specified namespace. - **Exec** into a pod and run a command. - **Run** a container image in a pod and optionally expose it. - **✅ Namespaces**: List Kubernetes Namespaces. - **✅ Events**: View Kubernetes events in all namespaces or in a specific namespace. - **✅ Projects**: List OpenShift Projects. - **☸️ Helm**: - **Install** a Helm chart in the current or provided namespace. - **List** Helm releases in all namespaces or in a specific namespace. - **Uninstall** a Helm release in the current or provided namespace. Unlike other Kubernetes MCP server implementations, this **IS NOT** just a wrapper around `kubectl` or `helm` command-line tools. It is a **Go-based native implementation** that interacts directly with the Kubernetes API server. There is **NO NEED** for external dependencies or tools to be installed on the system. If you're using the native binaries you don't need to have Node or Python installed on your system. - **✅ Lightweight**: The server is distributed as a single native binary for Linux, macOS, and Windows. - **✅ High-Performance / Low-Latency**: Directly interacts with the Kubernetes API server without the overhead of calling and waiting for external commands. - **✅ Cross-Platform**: Available as a native binary for Linux, macOS, and Windows, as well as an npm package, a Python package, and container/Docker image. - **✅ Configurable**: Supports [command-line arguments](#configuration) to configure the server behavior. - **✅ Well tested**: The server has an extensive test suite to ensure its reliability and correctness across different Kubernetes environments. ## 🚀 Getting Started <a id="getting-started"></a> ### Requirements - Access to a Kubernetes cluster. ### Claude Desktop #### Using npx If you have npm installed, this is the fastest way to get started with `kubernetes-mcp-server` on Claude Desktop. Open your `claude_desktop_config.json` and add the mcp server to the list of `mcpServers`: ``` json { "mcpServers": { "kubernetes": { "command": "npx", "args": [ "-y", "kubernetes-mcp-server@latest" ] } } } ``` ### VS Code / VS Code Insiders Install the Kubernetes MCP server extension in VS Code Insiders by pressing the following link: [<img src="https://img.shields.io/badge/VS_Code-VS_Code?style=flat-square&label=Install%20Server&color=0098FF" alt="Install in VS Code">](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522kubernetes%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522kubernetes-mcp-server%2540latest%2522%255D%257D) [<img alt="Install in VS Code Insiders" src="https://img.shields.io/badge/VS_Code_Insiders-VS_Code_Insiders?style=flat-square&label=Install%20Server&color=24bfa5">](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522kubernetes%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522kubernetes-mcp-server%2540latest%2522%255D%257D) Alternatively, you can install the extension manually by running the following command: ```shell # For VS Code code --add-mcp '{"name":"kubernetes","command":"npx","args":["kubernetes-mcp-server@latest"]}' # For VS Code Insiders code-insiders --add-mcp '{"name":"kubernetes","command":"npx","args":["kubernetes-mcp-server@latest"]}' ``` ### Goose CLI [Goose CLI](https://blog.marcnuri.com/goose-on-machine-ai-agent-cli-introduction) is the easiest (and cheapest) way to get rolling with artificial intelligence (AI) agents. #### Using npm If you have npm installed, this is the fastest way to get started with `kubernetes-mcp-server`. Open your goose `config.yaml` and add the mcp server to the list of `mcpServers`: ```yaml extensions: kubernetes: command: npx args: - -y - kubernetes-mcp-server@latest ``` ## 🎥 Demos <a id="demos"></a> ### Diagnosing and automatically fixing an OpenShift Deployment Demo showcasing how Kubernetes MCP server is leveraged by Claude Desktop to automatically diagnose and fix a deployment in OpenShift without any user assistance. https://github.com/user-attachments/assets/a576176d-a142-4c19-b9aa-a83dc4b8d941 ### _Vibe Coding_ a simple game and deploying it to OpenShift In this demo, I walk you through the process of _Vibe Coding_ a simple game using VS Code and how to leverage [Podman MCP server](https://github.com/manusa/podman-mcp-server) and Kubernetes MCP server to deploy it to OpenShift. <a href="https://www.youtube.com/watch?v=l05jQDSrzVI" target="_blank"> <img src="docs/images/vibe-coding.jpg" alt="Vibe Coding: Build & Deploy a Game on Kubernetes" width="240" /> </a> ### Supercharge GitHub Copilot with Kubernetes MCP Server in VS Code - One-Click Setup! In this demo, I'll show you how to set up Kubernetes MCP server in VS code just by clicking a link. <a href="https://youtu.be/AI4ljYMkgtA" target="_blank"> <img src="docs/images/kubernetes-mcp-server-github-copilot.jpg" alt="Supercharge GitHub Copilot with Kubernetes MCP Server in VS Code - One-Click Setup!" width="240" /> </a> ## ⚙️ Configuration <a id="configuration"></a> The Kubernetes MCP server can be configured using command line (CLI) arguments. You can run the CLI executable either by using `npx`, `uvx`, or by downloading the [latest release binary](https://github.com/manusa/kubernetes-mcp-server/releases/latest). ```shell # Run the Kubernetes MCP server using npx (in case you have npm and node installed) npx kubernetes-mcp-server@latest --help ``` ```shell # Run the Kubernetes MCP server using uvx (in case you have uv and python installed) uvx kubernetes-mcp-server@latest --help ``` ```shell # Run the Kubernetes MCP server using the latest release binary ./kubernetes-mcp-server --help ``` ### Configuration Options | Option | Description | |-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `--http-port` | Starts the MCP server in Streamable HTTP mode and listens on the specified port (path /mcp). | | `--sse-port` | Starts the MCP server in Server-Sent Event (SSE) mode and listens on the specified port (path /sse). | | `--log-level` | Sets the logging level (values [from 0-9](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md)). Similar to [kubectl logging levels](https://kubernetes.io/docs/reference/kubectl/quick-reference/#kubectl-output-verbosity-and-debugging). | | `--kubeconfig` | Path to the Kubernetes configuration file. If not provided, it will try to resolve the configuration (in-cluster, default location, etc.). | | `--list-output` | Output format for resource list operations (one of: yaml, table) (default "table") | | `--read-only` | If set, the MCP server will run in read-only mode, meaning it will not allow any write operations (create, update, delete) on the Kubernetes cluster. This is useful for debugging or inspecting the cluster without making changes. | | `--disable-destructive` | If set, the MCP server will disable all destructive operations (delete, update, etc.) on the Kubernetes cluster. This is useful for debugging or inspecting the cluster without accidentally making changes. This option has no effect when `--read-only` is used. | ## 🛠️ Tools <a id="tools"></a> ### `configuration_view` Get the current Kubernetes configuration content as a kubeconfig YAML **Parameters:** - `minified` (`boolean`, optional, default: `true`) - Return a minified version of the configuration - If `true`, keeps only the current-context and relevant configuration pieces - If `false`, returns all contexts, clusters, auth-infos, and users ### `events_list` List all the Kubernetes events in the current cluster from all namespaces **Parameters:** - `namespace` (`string`, optional) - Namespace to retrieve the events from. If not provided, will list events from all namespaces ### `helm_install` Install a Helm chart in the current or provided namespace with the provided name and chart **Parameters:** - `chart` (`string`, required) - Name of the Helm chart to install - Can be a local path or a remote URL - Example: `./my-chart.tgz` or `https://example.com/my-chart.tgz` - `values` (`object`, optional) - Values to pass to the Helm chart - Example: `{"key": "value"}` - `name` (`string`, optional) - Name of the Helm release - Random name if not provided - `namespace` (`string`, optional) - Namespace to install the Helm chart in - If not provided, will use the configured namespace ### `helm_list` List all the Helm releases in the current or provided namespace (or in all namespaces if specified) **Parameters:** - `namespace` (`string`, optional) - Namespace to list the Helm releases from - If not provided, will use the configured namespace - `all_namespaces` (`boolean`, optional) - If `true`, will list Helm releases from all namespaces - If `false`, will list Helm releases from the specified namespace ### `helm_uninstall` Uninstall a Helm release in the current or provided namespace with the provided name **Parameters:** - `name` (`string`, required) - Name of the Helm release to uninstall - `namespace` (`string`, optional) - Namespace to uninstall the Helm release from - If not provided, will use the configured namespace ### `namespaces_list` List all the Kubernetes namespaces in the current cluster **Parameters:** None ### `pods_delete` Delete a Kubernetes Pod in the current or provided namespace with the provided name **Parameters:** - `name` (`string`, required) - Name of the Pod to delete - `namespace` (`string`, required) - Namespace to delete the Pod from ### `pods_exec` Execute a command in a Kubernetes Pod in the current or provided namespace with the provided name and command **Parameters:** - `command` (`string[]`, required) - Command to execute in the Pod container - First item is the command, rest are arguments - Example: `["ls", "-l", "/tmp"]` - `name` (string, required) - Name of the Pod - `namespace` (string, required) - Namespace of the Pod - `container` (`string`, optional) - Name of the Pod container to get logs from ### `pods_get` Get a Kubernetes Pod in the current or provided namespace with the provided name **Parameters:** - `name` (`string`, required) - Name of the Pod - `namespace` (`string`, required) - Namespace to get the Pod from ### `pods_list` List all the Kubernetes pods in the current cluster from all namespaces **Parameters:** - `labelSelector` (`string`, optional) - Kubernetes label selector (e.g., 'app=myapp,env=prod' or 'app in (myapp,yourapp)'). Use this option to filter the pods by label ### `pods_list_in_namespace` List all the Kubernetes pods in the specified namespace in the current cluster **Parameters:** - `namespace` (`string`, required) - Namespace to list pods from - `labelSelector` (`string`, optional) - Kubernetes label selector (e.g., 'app=myapp,env=prod' or 'app in (myapp,yourapp)'). Use this option to filter the pods by label ### `pods_log` Get the logs of a Kubernetes Pod in the current or provided namespace with the provided name **Parameters:** - `name` (`string`, required) - Name of the Pod to get logs from - `namespace` (`string`, required) - Namespace to get the Pod logs from - `container` (`string`, optional) - Name of the Pod container to get logs from ### `pods_run` Run a Kubernetes Pod in the current or provided namespace with the provided container image and optional name **Parameters:** - `image` (`string`, required) - Container Image to run in the Pod - `namespace` (`string`, required) - Namespace to run the Pod in - `name` (`string`, optional) - Name of the Pod (random name if not provided) - `port` (`number`, optional) - TCP/IP port to expose from the Pod container - No port exposed if not provided ### `projects_list` List all the OpenShift projects in the current cluster ### `resources_create_or_update` Create or update a Kubernetes resource in the current cluster by providing a YAML or JSON representation of the resource **Parameters:** - `resource` (`string`, required) - A JSON or YAML containing a representation of the Kubernetes resource - Should include top-level fields such as apiVersion, kind, metadata, and spec **Common apiVersion and kind include:** - v1 Pod - v1 Service - v1 Node - apps/v1 Deployment - networking.k8s.io/v1 Ingress ### `resources_delete` Delete a Kubernetes resource in the current cluster **Parameters:** - `apiVersion` (`string`, required) - apiVersion of the resource (e.g., `v1`, `apps/v1`, `networking.k8s.io/v1`) - `kind` (`string`, required) - kind of the resource (e.g., `Pod`, `Service`, `Deployment`, `Ingress`) - `name` (`string`, required) - Name of the resource - `namespace` (`string`, optional) - Namespace to delete the namespaced resource from - Ignored for cluster-scoped resources - Uses configured namespace if not provided ### `resources_get` Get a Kubernetes resource in the current cluster **Parameters:** - `apiVersion` (`string`, required) - apiVersion of the resource (e.g., `v1`, `apps/v1`, `networking.k8s.io/v1`) - `kind` (`string`, required) - kind of the resource (e.g., `Pod`, `Service`, `Deployment`, `Ingress`) - `name` (`string`, required) - Name of the resource - `namespace` (`string`, optional) - Namespace to retrieve the namespaced resource from - Ignored for cluster-scoped resources - Uses configured namespace if not provided ### `resources_list` List Kubernetes resources and objects in the current cluster **Parameters:** - `apiVersion` (`string`, required) - apiVersion of the resources (e.g., `v1`, `apps/v1`, `networking.k8s.io/v1`) - `kind` (`string`, required) - kind of the resources (e.g., `Pod`, `Service`, `Deployment`, `Ingress`) - `namespace` (`string`, optional) - Namespace to retrieve the namespaced resources from - Ignored for cluster-scoped resources - Lists resources from all namespaces if not provided - `labelSelector` (`string`, optional) - Kubernetes label selector (e.g., 'app=myapp,env=prod' or 'app in (myapp,yourapp)'). Use this option to filter the pods by label. ## 🧑‍💻 Development <a id="development"></a> ### Running with mcp-inspector Compile the project and run the Kubernetes MCP server with [mcp-inspector](https://modelcontextprotocol.io/docs/tools/inspector) to inspect the MCP server. ```shell # Compile the project make build # Run the Kubernetes MCP server with mcp-inspector npx @modelcontextprotocol/inspector@latest $(pwd)/kubernetes-mcp-server ``` ", Assign "at most 3 tags" to the expected json: {"id":"13888","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"