Skip to content
Back to search

mcp-server-kubernetes

MCP Server for kubernetes management commands

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Flux159/mcp-server-kubernetes with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Flux159/mcp-server-kubernetes'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/flux159--mcp-server-kubernetes/badge.svg)](/listings/flux159--mcp-server-kubernetes)

HTML

<a href="/listings/flux159--mcp-server-kubernetes"><img src="/api/listings/flux159--mcp-server-kubernetes/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Prerequisites

Before using this MCP server with any tool, make sure you have:

1. kubectl installed and in your PATH 2. A valid kubeconfig file with contexts configured 3. Access to a Kubernetes cluster configured for kubectl (e.g. minikube, Rancher Desktop, GKE, etc.) 4. Helm v3 installed and in your PATH (no Tiller required). Optional if you don't plan to use Helm.

You can verify your connection by running `kubectl get pods` in a terminal to ensure you can connect to your cluster without credential issues.

By default, the server loads kubeconfig from `~/.kube/config`. For additional authentication options (environment variables, custom paths, etc.), see [ADVANCED_README.md](ADVANCED_README.md).

Claude Code

Add the MCP server to Claude Code using the built-in command:

claude mcp add kubernetes -- npx mcp-server-kubernetes

This will automatically configure the server in your Claude Code MCP settings.

Codex

Add the MCP server to [Codex CLI](https://developers.openai.com/codex/cli/) using the built-in command:

codex mcp add kubernetes -- npx mcp-server-kubernetes

This registers the server globally in `~/.codex/config.toml` and makes its tools available in all Codex sessions.

Claude Desktop

Add the following configuration to your Claude Desktop config file:

{
  "mcpServers": {
    "kubernetes": {
      "command": "npx",
      "args": ["mcp-server-kubernetes"]
    }
  }
}

Claude Desktop Connector via mcpb

MCP Server Kubernetes is also available as a [mcpb](https://github.com/anthropics/mcpb) (formerly dxt) extension. In Claude Desktop, go to Settings (`Cmd+,` on Mac) -> Extensions -> Browse Extensions and scroll to find mcp-server-kubernetes in the modal. Install it & it will install & utilize kubectl via command line & your kubeconfig.

To manually install, you can also get the .mcpb by going to the latest [Release](https://github.com/Flux159/mcp-server-kubernetes/releases) and downloading it.

VS Code

For VS Code integration, you can use the MCP server with extensions that support the Model Context Protocol:

1. Install a compatible MCP extension (such as Claude Dev or similar MCP clients) 2. Configure the extension to use this server:

{
  "mcpServers": {
    "kubernetes": {
      "command": "npx",
      "args": ["mcp-server-kubernetes"],
      "description": "Kubernetes cluster management and operations"
    }
  }
}

Cursor

Cursor supports MCP servers through its AI integration. Add the server to your Cursor MCP configuration:

{
  "mcpServers": {
    "kubernetes": {
      "command": "npx",
      "args": ["mcp-server-kubernetes"]
    }
  }
}

The server will automatically connect to your current kubectl context. You can verify the connection by asking the AI assistant to list your pods or create a test deployment.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 570 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # MCP Server Kubernetes
  2. [![CI](https://github.com/Flux159/mcp-server-kubernetes/actions/workflows/ci.yml/badge.svg)](https://github.com/yourusername/mcp-server-kubernetes/actions/workflows/ci.yml)
  3. [![Language](https://img.shields.io/github/languages/top/Flux159/mcp-server-kubernetes)](https://github.com/yourusername/mcp-server-kubernetes)
  4. [![Kubernetes](https://img.shields.io/badge/kubernetes-%23326ce5.svg?style=flat&logo=kubernetes&logoColor=white)](https://kubernetes.io/)
  5. [![Docker](https://img.shields.io/badge/docker-%230db7ed.svg?style=flat&logo=docker&logoColor=white)](https://www.docker.com/)
  6. [![Stars](https://img.shields.io/github/stars/Flux159/mcp-server-kubernetes)](https://github.com/Flux159/mcp-server-kubernetes/stargazers)
  7. [![Issues](https://img.shields.io/github/issues/Flux159/mcp-server-kubernetes)](https://github.com/Flux159/mcp-server-kubernetes/issues)
  8. [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/Flux159/mcp-server-kubernetes/pulls)
  9. [![Last Commit](https://img.shields.io/github/last-commit/Flux159/mcp-server-kubernetes)](https://github.com/Flux159/mcp-server-kubernetes/commits/main)
  10. <p align="center">
  11. <img src="https://raw.githubusercontent.com/Flux159/mcp-server-kubernetes/refs/heads/main/icon.png" width="200">
  12. </p>
  13. MCP Server that can connect to a Kubernetes cluster and manage it. Supports loading kubeconfig from multiple sources in priority order.
  14. https://github.com/user-attachments/assets/f25f8f4e-4d04-479b-9ae0-5dac452dd2ed
  15. ## Installation & Usage
  16. ### Prerequisites
  17. Before using this MCP server with any tool, make sure you have:
  18. 1. kubectl installed and in your PATH
  19. 2. A valid kubeconfig file with contexts configured
  20. 3. Access to a Kubernetes cluster configured for kubectl (e.g. minikube, Rancher Desktop, GKE, etc.)
  21. 4. Helm v3 installed and in your PATH (no Tiller required). Optional if you don't plan to use Helm.
  22. You can verify your connection by running `kubectl get pods` in a terminal to ensure you can connect to your cluster without credential issues.
  23. By default, the server loads kubeconfig from `~/.kube/config`. For additional authentication options (environment variables, custom paths, etc.), see [ADVANCED_README.md](ADVANCED_README.md).
  24. ### Claude Code
  25. Add the MCP server to Claude Code using the built-in command:
  26. ```bash
  27. claude mcp add kubernetes -- npx mcp-server-kubernetes
  28. ```
  29. This will automatically configure the server in your Claude Code MCP settings.
  30. ### Codex
  31. Add the MCP server to [Codex CLI](https://developers.openai.com/codex/cli/) using the built-in command:
  32. ```bash
  33. codex mcp add kubernetes -- npx mcp-server-kubernetes
  34. ```
  35. This registers the server globally in `~/.codex/config.toml` and makes its tools available in all Codex sessions.
  36. ### Claude Desktop
  37. Add the following configuration to your Claude Desktop config file:
  38. ```json
  39. {
  40. "mcpServers": {
  41. "kubernetes": {
  42. "command": "npx",
  43. "args": ["mcp-server-kubernetes"]
  44. }
  45. }
  46. }
  47. ```
  48. ### Claude Desktop Connector via mcpb
  49. MCP Server Kubernetes is also available as a [mcpb](https://github.com/anthropics/mcpb) (formerly dxt) extension. In Claude Desktop, go to Settings (`Cmd+,` on Mac) -> Extensions -> Browse Extensions and scroll to find mcp-server-kubernetes in the modal. Install it & it will install & utilize kubectl via command line & your kubeconfig.
  50. To manually install, you can also get the .mcpb by going to the latest [Release](https://github.com/Flux159/mcp-server-kubernetes/releases) and downloading it.
  51. ### VS Code
  52. [![Install Kubernetes MCP in VS Code](https://img.shields.io/badge/Install%20Kubernetes%20MCP%20in%20VS%20Code-blue?logo=visualstudiocode)](vscode:mcp/install?%7B%22name%22%3A%20%22kubernetes%22%2C%20%22type%22%3A%20%22stdio%22%2C%20%22command%22%3A%20%22npx%22%2C%20%22args%22%3A%20%5B%22mcp-server-kubernetes%22%5D%7D)
  53. VS Code has built-in MCP support. Use the one-click install button above, or add the server to `.vscode/mcp.json` in your workspace (or to your user `mcp.json` via **MCP: Open User Configuration**):
  54. ```json
  55. {
  56. "servers": {
  57. "kubernetes": {
  58. "type": "stdio",
  59. "command": "npx",
  60. "args": ["mcp-server-kubernetes"]
  61. }
  62. }
  63. }
  64. ```
  65. ### Cursor
  66. Cursor supports MCP servers through its AI integration. Add the server to `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (project):
  67. ```json
  68. {
  69. "mcpServers": {
  70. "kubernetes": {
  71. "command": "npx",
  72. "args": ["mcp-server-kubernetes"]
  73. }
  74. }
  75. }
  76. ```
  77. The server will automatically connect to your current kubectl context. You can verify the connection by asking the AI assistant to list your pods or create a test deployment.
  78. ### Muse Code
  79. [Muse Code](https://dev.meta.ai/docs/muse-code/extending#mcp) reads MCP servers from the `mcp_servers` block of `~/.config/muse/settings.json`. The file must include `"schema_version": 1`:
  80. ```json
  81. {
  82. "schema_version": 1,
  83. "mcp_servers": {
  84. "kubernetes": {
  85. "transport": "stdio",
  86. "command": "npx",
  87. "args": ["mcp-server-kubernetes"]
  88. }
  89. }
  90. }
  91. ```
  92. To connect over Streamable HTTP instead, first start the server in HTTP mode (it serves `/mcp` on port `3000` by default; see [Streamable HTTP Transport](ADVANCED_README.md#streamable-http-transport)):
  93. ```bash
  94. ENABLE_UNSAFE_STREAMABLE_HTTP_TRANSPORT=1 npx mcp-server-kubernetes
  95. ```
  96. Then point Muse Code at that endpoint with the `streamable_http` transport (`headers` is optional):
  97. ```json
  98. {
  99. "schema_version": 1,
  100. "mcp_servers": {
  101. "kubernetes": {
  102. "transport": "streamable_http",
  103. "url": "http://localhost:3000/mcp",
  104. "mode": "optional"
  105. }
  106. }
  107. }
  108. ```
  109. `"mode": "optional"` lets Muse Code start with a warning if the HTTP server isn't running, instead of aborting.
  110. Start a new Muse Code session after editing the file, then run `/mcp` to confirm the `kubernetes` server and its tools are connected.
  111. ## Usage with mcp-chat
  112. [mcp-chat](https://github.com/Flux159/mcp-chat) is a CLI chat client for MCP servers. You can use it to interact with the Kubernetes server.
  113. ```shell
  114. npx mcp-chat --server "npx mcp-server-kubernetes"
  115. ```
  116. Alternatively, pass it your existing Claude Desktop configuration file from above (Linux should pass the correct path to config):
  117. Mac:
  118. ```shell
  119. npx mcp-chat --config "~/Library/Application Support/Claude/claude_desktop_config.json"
  120. ```
  121. Windows:
  122. ```shell
  123. npx mcp-chat --config "%APPDATA%\Claude\claude_desktop_config.json"
  124. ```
  125. ## Features
  126. - [x] Connect to a Kubernetes cluster
  127. - [x] Unified kubectl API for managing resources
  128. - Get or list resources with `kubectl_get`
  129. - Describe resources with `kubectl_describe`
  130. - List resources with `kubectl_get`
  131. - Create resources with `kubectl_create`
  132. - Apply YAML manifests with `kubectl_apply`
  133. - Delete resources with `kubectl_delete`
  134. - Get logs with `kubectl_logs`
  135. - Manage kubectl contexts with `kubectl_context`
  136. - Explain Kubernetes resources with `explain_resource`
  137. - List API resources with `list_api_resources`
  138. - Scale resources with `kubectl_scale`
  139. - Update field(s) of a resource with `kubectl_patch`
  140. - Manage deployment rollouts with `kubectl_rollout`
  141. - Execute any kubectl command with `kubectl_generic`
  142. - Verify connection with `ping`
  143. - [x] Advanced operations
  144. - Scale deployments with `kubectl_scale` (replaces legacy `scale_deployment`)
  145. - Port forward to pods and services with `port_forward`
  146. - Run Helm operations
  147. - Install, upgrade, and uninstall charts
  148. - Support for custom values, repositories, and versions
  149. - Template-based installation (`helm_template_apply`) to bypass authentication issues
  150. - Template-based uninstallation (`helm_template_uninstall`) to bypass authentication issues
  151. - Pod cleanup operations
  152. - Clean up problematic pods (`cleanup_pods`) in states: Evicted, ContainerStatusUnknown, Completed, Error, ImagePullBackOff, CrashLoopBackOff
  153. - Node management operations
  154. - Cordoning, draining, and uncordoning nodes (`node_management`) for maintenance and scaling operations
  155. - [x] Troubleshooting Prompt (`k8s-diagnose`)
  156. - Guides through a systematic Kubernetes troubleshooting flow for pods based on a keyword and optional namespace.
  157. - [x] Non-destructive mode for read and create/update-only access to clusters
  158. - [x] Secrets masking for security (masks sensitive data in `kubectl get secrets` commands, does not affect logs)
  159. - [x] **OpenTelemetry Observability** (opt-in)
  160. - Distributed tracing for all tool calls
  161. - Export to Jaeger, Tempo, Grafana, or any OTLP backend
  162. - Configurable sampling strategies
  163. - Rich span attributes (tool name, duration, K8s context, errors)
  164. - See [docs/OBSERVABILITY.md](docs/OBSERVABILITY.md) for details
  165. ## Observability
  166. The MCP Kubernetes server includes optional **OpenTelemetry integration** for comprehensive observability. This feature is disabled by default and can be enabled via environment variables or Helm configuration.
  167. ### Quick Start
  168. Enable observability with environment variables:
  169. ```bash
  170. export ENABLE_TELEMETRY=true
  171. export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317
  172. npx mcp-server-kubernetes
  173. ```
  174. ### What Gets Traced
  175. - **All tool calls**: kubectl_get, kubectl_apply, kubectl_logs, etc.
  176. - **Execution duration**: How long each operation takes
  177. - **Success/failure status**: Automatic error tracking
  178. - **Kubernetes context**: Namespace, context, resource type
  179. - **Rich metadata**: Host, process, and custom attributes
  180. ### Backends Supported
  181. Works with any OTLP-compatible backend:
  182. - **Jaeger** (open source)
  183. - **Grafana Tempo** (open source)
  184. - **Grafana Cloud** (commercial)
  185. - **Datadog**, **New Relic**, **Honeycomb**, **Lightstep**, **AWS X-Ray**
  186. ### Configuration
  187. See **[docs/OBSERVABILITY.md](docs/OBSERVABILITY.md)** for comprehensive documentation including:
  188. - Configuration options
  189. - Deployment examples (Kubernetes, Helm, Claude Code)
  190. - Sampling strategies
  191. - Production best practices
  192. - Troubleshooting guide
  193. ### Example with Jaeger
  194. ```bash
  195. # Start Jaeger
  196. docker run -d --name jaeger \
  197. -e COLLECTOR_OTLP_ENABLED=true \
  198. -p 16686:16686 \
  199. -p 4317:4317 \
  200. jaegertracing/all-in-one:latest
  201. # Enable telemetry
  202. export ENABLE_TELEMETRY=true
  203. export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317
  204. export OTEL_TRACES_SAMPLER=always_on
  205. # Run server
  206. npx mcp-server-kubernetes
  207. # View traces: http://localhost:16686
  208. ```
  209. ## Prompts
  210. The MCP Kubernetes server includes specialized prompts to assist with common diagnostic operations.
  211. ### /k8s-diagnose Prompt
  212. This prompt provides a systematic troubleshooting flow for Kubernetes pods. It accepts a `keyword` to identify relevant pods and an optional `namespace` to narrow the search.
  213. The prompt's output will guide you through an autonomous troubleshooting flow, providing instructions for identifying issues, collecting evidence, and suggesting remediation steps.
  214. ## Troubleshooting
  215. ### `spawnSync kubectl ENOENT` on macOS (Claude Desktop / GUI apps)
  216. If `kubectl` works in your terminal but the server fails with an error like:
  217. ```
  218. Failed to execute kubectl get command: ... spawnSync kubectl ENOENT
  219. ```
  220. the server process cannot find `kubectl` in its `PATH`. This is common on macOS: GUI
  221. applications (such as Claude Desktop) do not inherit the `PATH` from your shell profile
  222. (`~/.zshrc`, `~/.bashrc`), so a `kubectl` installed in `/usr/local/bin` or
  223. `/opt/homebrew/bin` is invisible to the bundled extension — even though `which kubectl`
  224. works in a terminal.
  225. Either of the following resolves it:
  226. - **Run it as a local MCP server via the developer config** instead of the bundled
  227. extension. The developer config lets you set `env` for the server (see
  228. [Advanced](#advanced)), which inherits a fuller environment.
  229. - **Set an explicit `PATH`** for the server in your client config so it includes the
  230. directory that contains `kubectl` (for example `/usr/local/bin` or
  231. `/opt/homebrew/bin`):
  232. ```json
  233. {
  234. "mcpServers": {
  235. "kubernetes": {
  236. "command": "npx",
  237. "args": ["mcp-server-kubernetes"],
  238. "env": {
  239. "PATH": "/usr/local/bin:/opt/homebrew/bin:/usr/bin:/bin:/usr/sbin:/sbin"
  240. }
  241. }
  242. }
  243. }
  244. ```
  245. The same applies to `helm` if you use Helm operations: make sure its directory is on the
  246. `PATH` you pass to the server.
  247. ## Local Development
  248. Make sure that you have [bun installed](https://bun.sh/docs/installation). Clone the repo & install dependencies:
  249. ```bash
  250. git clone https://github.com/Flux159/mcp-server-kubernetes.git
  251. cd mcp-server-kubernetes
  252. bun install
  253. ```
  254. ### Development Workflow
  255. 1. Start the server in development mode (watches for file changes):
  256. ```bash
  257. bun run dev
  258. ```
  259. 2. Run unit tests:
  260. ```bash
  261. bun run test
  262. ```
  263. 3. Build the project:
  264. ```bash
  265. bun run build
  266. ```
  267. 4. Local Testing with [Inspector](https://github.com/modelcontextprotocol/inspector)
  268. ```bash
  269. npx @modelcontextprotocol/inspector node dist/index.js
  270. # Follow further instructions on terminal for Inspector link
  271. ```
  272. 5. Local testing with Claude Desktop
  273. ```json
  274. {
  275. "mcpServers": {
  276. "mcp-server-kubernetes": {
  277. "command": "node",
  278. "args": ["/path/to/your/mcp-server-kubernetes/dist/index.js"]
  279. }
  280. }
  281. }
  282. ```
  283. 6. Local testing with [mcp-chat](https://github.com/Flux159/mcp-chat)
  284. ```bash
  285. bun run chat
  286. ```
  287. ## Contributing
  288. See the [CONTRIBUTING.md](CONTRIBUTING.md) file for details.
  289. ## Advanced
  290. ### Non-Destructive Mode
  291. You can run the server in a non-destructive mode that disables all destructive operations (delete pods, delete deployments, delete namespaces, etc.):
  292. ```shell
  293. ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS=true npx mcp-server-kubernetes
  294. ```
  295. For Claude Desktop configuration with non-destructive mode:
  296. ```json
  297. {
  298. "mcpServers": {
  299. "kubernetes-non-destructive": {
  300. "command": "npx",
  301. "args": ["mcp-server-kubernetes"],
  302. "env": {
  303. "ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS": "true"
  304. }
  305. }
  306. }
  307. }
  308. ```
  309. ### Commands Available in Non-Destructive Mode
  310. All read-only and resource creation/update operations remain available:
  311. - Resource Information: `kubectl_get`, `kubectl_describe`, `kubectl_logs`, `explain_resource`, `list_api_resources`
  312. - Resource Creation/Modification: `kubectl_apply`, `kubectl_create`, `kubectl_scale`, `kubectl_patch`, `kubectl_rollout`
  313. - Helm Operations: `install_helm_chart`, `upgrade_helm_chart`, `helm_template_apply`, `helm_template_uninstall`
  314. - Connectivity: `port_forward`, `stop_port_forward`
  315. - Context Management: `kubectl_context`
  316. ### Commands Disabled in Non-Destructive Mode
  317. The following destructive operations are disabled:
  318. - `kubectl_delete`: Deleting any Kubernetes resources
  319. - `uninstall_helm_chart`: Uninstalling Helm charts
  320. - `cleanup`: Cleanup of managed resources
  321. - `cleanup_pods`: Cleaning up problematic pods
  322. - `node_management`: Node management operations (can drain nodes)
  323. - `kubectl_generic`: General kubectl command access (may include destructive operations)
  324. - `exec_in_pod`: Arbitrary command execution inside a pod (can read service-account tokens and change state)
  325. For additional advanced features, see the [ADVANCED_README.md](ADVANCED_README.md) and also the [docs](https://github.com/Flux159/mcp-server-kubernetes/tree/main/docs) folder for specific information on `helm_install`, `helm_template_apply`, node management & pod cleanup.
  326. ### Read-Only Mode
  327. For strictly read-only access (no create, update, or delete), run the server with
  328. `ALLOW_ONLY_READONLY_TOOLS=true`. Unlike non-destructive mode — which still allows
  329. create/update operations such as `kubectl_apply`, `kubectl_scale`, and Helm install/upgrade —
  330. read-only mode exposes only the 8 read-only tools and blocks every write operation:
  331. ```shell
  332. ALLOW_ONLY_READONLY_TOOLS=true npx mcp-server-kubernetes
  333. ```
  334. For Claude Desktop configuration with read-only mode:
  335. ```json
  336. {
  337. "mcpServers": {
  338. "kubernetes-readonly": {
  339. "command": "npx",
  340. "args": ["mcp-server-kubernetes"],
  341. "env": {
  342. "ALLOW_ONLY_READONLY_TOOLS": "true"
  343. }
  344. }
  345. }
  346. }
  347. ```
  348. ### Commands Available in Read-Only Mode
  349. Only the following read-only operations are available:
  350. - `kubectl_get`
  351. - `kubectl_describe`
  352. - `kubectl_logs`
  353. - `kubectl_context`
  354. - `kubectl_reconnect`
  355. - `explain_resource`
  356. - `list_api_resources`
  357. - `ping`
  358. ## Architecture
  359. See this [DeepWiki link](https://deepwiki.com/Flux159/mcp-server-kubernetes) for a more indepth architecture overview created by Devin.
  360. This section describes the high-level architecture of the MCP Kubernetes server.
  361. ### Request Flow
  362. The sequence diagram below illustrates how requests flow through the system:
  363. ```mermaid
  364. sequenceDiagram
  365. participant Client
  366. participant Transport as Transport Layer
  367. participant Server as MCP Server
  368. participant Filter as Tool Filter
  369. participant Handler as Request Handler
  370. participant K8sManager as KubernetesManager
  371. participant K8s as Kubernetes API
  372. Note over Transport: StdioTransport or<br>SSE Transport
  373. Client->>Transport: Send Request
  374. Transport->>Server: Forward Request
  375. alt Tools Request
  376. Server->>Filter: Filter available tools
  377. Note over Filter: Remove destructive tools<br>if in non-destructive mode
  378. Filter->>Handler: Route to tools handler
  379. alt kubectl operations
  380. Handler->>K8sManager: Execute kubectl operation
  381. K8sManager->>K8s: Make API call
  382. else Helm operations
  383. Handler->>K8sManager: Execute Helm operation
  384. K8sManager->>K8s: Make API call
  385. else Port Forward operations
  386. Handler->>K8sManager: Set up port forwarding
  387. K8sManager->>K8s: Make API call
  388. end
  389. K8s-->>K8sManager: Return result
  390. K8sManager-->>Handler: Process response
  391. Handler-->>Server: Return tool result
  392. else Resource Request
  393. Server->>Handler: Route to resource handler
  394. Handler->>K8sManager: Get resource data
  395. K8sManager->>K8s: Query API
  396. K8s-->>K8sManager: Return data
  397. K8sManager-->>Handler: Format response
  398. Handler-->>Server: Return resource data
  399. end
  400. Server-->>Transport: Send Response
  401. Transport-->>Client: Return Final Response
  402. ```
  403. See this [DeepWiki link](https://deepwiki.com/Flux159/mcp-server-kubernetes) for a more indepth architecture overview created by Devin.
  404. ## Publishing new release
  405. Go to the [releases page](https://github.com/Flux159/mcp-server-kubernetes/releases), click on "Draft New Release", click "Choose a tag" and create a new tag by typing out a new version number using "v{major}.{minor}.{patch}" semver format. Then, write a release title "Release v{major}.{minor}.{patch}" and description / changelog if necessary and click "Publish Release".
  406. This will create a new tag which will trigger a new release build via the cd.yml workflow. Once successful, the new release will be published to [npm](https://www.npmjs.com/package/mcp-server-kubernetes). Note that there is no need to update the package.json version manually, as the workflow will automatically update the version number in the package.json file & push a commit to main.
  407. ## Not planned
  408. Adding clusters to kubectx.
  409. ## Star History
  410. <a href="https://github.com/Flux159/rust-star-history">
  411. <picture>
  412. <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Flux159/mcp-server-kubernetes/star-history/star-history-dark.svg">
  413. <img alt="Star History Chart" src="https://raw.githubusercontent.com/Flux159/mcp-server-kubernetes/star-history/star-history.svg">
  414. </picture>
  415. </a>
  416. ## 🖊️ Cite
  417. If you find this repo useful, please cite:
  418. ```
  419. @software{Patel_MCP_Server_Kubernetes_2024,
  420. author = {Patel, Paras and Sonwalkar, Suyog},
  421. month = jul,
  422. title = {{MCP Server Kubernetes}},
  423. url = {https://github.com/Flux159/mcp-server-kubernetes},
  424. version = {2.5.0},
  425. year = {2024}
  426. }
  427. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.