MCP Server Kubernetes — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track Kubernetes API and operation coverage because cluster control is high impact

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Developers and platform/DevOps teams operating Kubernetes through an AI client.

What we know

A Kubernetes MCP server for resource inspection, kubectl and Helm operations, rollouts, logs and node management.

Maintenance / activity evidence

Observed Oct 2, 2026 (UTC)Bump version to 4.1.9

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Kubernetes RBAC of active context. Writes: Create/apply/delete/patch/scale; Helm install/upgrade/uninstall; Node maintenance.
Local kubeconfig
Sensitive access: Cluster state, Secrets/logs, Workloads

The server can perform broad cluster administration; use least-privilege RBAC and non-destructive mode when possible.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

1,594 repository stars · 39.4k package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

All limitations / Review context

What cluster read and write operations are exposed and documented?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

The server can perform broad cluster administration; use least-privilege RBAC and non-destructive mode when possible.
Kubernetes RBAC of active context.
Local kubeconfig
Cluster resources and logs are returned to the MCP client.
Reviewed write actions: Create/apply/delete/patch/scale; Helm install/upgrade/uninstall; Node maintenance
Sensitive access: Cluster state, Secrets/logs, Workloads
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Inherits active kubeconfig/RBAC permissions.
Secret masking does not protect all possible log output.
Many tools are destructive or administrative.

Original activity observations

2026-10-02T04:57:55Z: Bump version to 4.1.9

Technical identity

github.com/flux159/mcp-server-kubernetes

Exact implementation source: https://github.com/flux159/mcp-server-kubernetes ↗
Reviewed resource type: MCP Server
Repository identity: Flux159/mcp-server-kubernetes
Package identity: npm:mcp-server-kubernetes

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
flux159/mcp-server-kubernetes
Recorded repository material and project history.
Includes references whose attribution is not established.
Package registry ↗
mcp-server-kubernetes
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
claude mcp add kubernetes -- npx mcp-server-kubernetes
Configure / authenticate
Publisher instructions
Requires kubectl on PATH and working ~/.kube/config or KUBECONFIG_PATH; prefer ALLOW_ONLY_READONLY_TOOLS=true for initial setup.
Advanced configuration · claude desktop json · Publisher instructions
claude desktop json · Publisher instructions
{ "mcpServers": { "kubernetes": { "args": [ "mcp-server-kubernetes" ], "command": "npx" } } }
Check connection
Publisher instructions
First `kubectl get pods` validates kubeconfig outside MCP; then list pods via MCP as read-only credential check.
read only check · Publisher instructions
kubectl get pods
Remove / uninstall / revoke
MCP100 setup guide
`claude mcp remove kubernetes` removes client registration without touching cluster workloads.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove kubernetes

Official Documentation & Sources

What it does

A Kubernetes MCP server for resource inspection, kubectl and Helm operations, rollouts, logs and node management.

Capability: Cloud & DevOps
Resource type: MCP Server
Industry: Software & Technology
Best fit: Developers and platform/DevOps teams operating Kubernetes through an AI client.

Representative uses

List and describe resources
Apply, patch, scale and delete resources
Read logs and run kubectl
Manage Helm and nodes

Limitations

Inherits active kubeconfig/RBAC permissions.
Secret masking does not protect all possible log output.
Many tools are destructive or administrative.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Local kubeconfig
Permissions: Kubernetes RBAC of active context.
Data handling: Cluster resources and logs are returned to the MCP client.
Cost: free
Risk and cautions: The server can perform broad cluster administration; use least-privilege RBAC and non-destructive mode when possible.

Access scope and cautions

Write actions: Create/apply/delete/patch/scale Helm install/upgrade/uninstall Node maintenance
Sensitive access: Cluster state Secrets/logs Workloads
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: List and describe resources; Apply, patch, scale and delete resources; Read logs and run kubectl; Manage Helm and nodes.

What setup and authentication are documented?

Recorded installation/entrypoint step: claude mcp add kubernetes -- npx mcp-server-kubernetes. Recorded transport: stdio. Prerequisites: kubectl-accessible Kubernetes cluster. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Uses kubectl/kubeconfig authentication.

Can it modify data or perform write operations?

Documented write actions include: Create/apply/delete/patch/scale; Helm install/upgrade/uninstall; Node maintenance. Recorded permission boundary: Kubernetes RBAC of active context.

What data-handling boundary should I consider?

Cluster resources and logs are returned to the MCP client. Recorded sensitive-access context: Cluster state; Secrets/logs; Workloads.

What limitations and risks should I check before use?

The server can perform broad cluster administration; use least-privilege RBAC and non-destructive mode when possible. Inherits active kubeconfig/RBAC permissions. Secret masking does not protect all possible log output. Many tools are destructive or administrative. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

Flux159 is listed as Community implementation in MCP100’s current evidence.