kubectl MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track Kubernetes command coverage and approval boundaries due cluster impact

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

Best fit

AI-assisted Kubernetes operations and troubleshooting

What we know

Kubernetes MCP exposing a broad tool set for workloads, networking, diagnostics, Cilium/Hubble and resource operations.

Maintenance / activity evidence

Observed Apr 8, 2026 (UTC)Improve README formatting and punctuation

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. Writes: Apply; Create; Patch; Scale; Restart; Delete; Copy; Label.
Kubeconfig.
Sensitive access: Cluster state, Potential secrets/workloads

Cluster-control authority can be very broad; use narrow RBAC and dedicated kubeconfigs.

Security source · repository notice ↗

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

Popularity

962 repository stars

Stars observed Oct 6, 2026.

No canonical package metric applied.

All limitations / Review context

Which kubectl operations and safety gates are currently 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.

Cluster-control authority can be very broad; use narrow RBAC and dedicated kubeconfigs.
Kubernetes RBAC.
Kubeconfig.
Reads/changes cluster resources.
Reviewed write actions: Apply; Create; Patch; Scale; Restart; Delete; Copy; Label
Sensitive access: Cluster state, Potential secrets/workloads
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Many destructive tools.
Authority is inherited from kubeconfig/RBAC.

Original activity observations

2026-04-08T22:37:48Z: Improve README formatting and punctuation

Technical identity

github.com/rohitg00/kubectl-mcp-server

Exact implementation source: https://github.com/rohitg00/kubectl-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: rohitg00/kubectl-mcp-server
Service endpoint: http://127.0.0.1:8000

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 ↗
rohitg00/kubectl-mcp-server
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
kubectl-mcp-server exposes Kubernetes operations to MCP clients.
publisher setup entry · Publisher instructions · Review before use
```
npx -y kubectl-mcp-server
```
Configure / authenticate
MCP100 setup guide
Use an existing Kubernetes kubeconfig with least-privilege read permissions; register npx as stdio in your MCP client. Alternative Python package is documented separately.
Check connection
Suggested check
List namespaces in a designated test cluster; do not deploy/delete resources.
Remove / uninstall / revoke
MCP100 setup guide
Remove the MCP server from the host configuration (Claude Code `claude mcp remove kubectl` only if that was the registered name). If installed globally via npm, run `npm uninstall -g kubectl-mcp-server`; if Python installed, use `python -m pip uninstall kubectl-mcp-server` in its owning environment.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Package / application uninstall · matching installation environment · MCP100 composed guide
npm uninstall -g kubectl-mcp-server

Official Documentation & Sources

What it does

Kubernetes MCP exposing a broad tool set for workloads, networking, diagnostics, Cilium/Hubble and resource operations.

Capability: Cloud & DevOps
Resource type: MCP Server
Industry: Software & Technology
Best fit: AI-assisted Kubernetes operations and troubleshooting

Representative uses

Inspect cluster state
Apply/patch/scale/restart/delete resources
Diagnose networking/DNS
Query usage

Limitations

Many destructive tools.
Authority is inherited from kubeconfig/RBAC.

Reviewed access

Access & risk

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

Authentication: Kubeconfig.
Permissions: Kubernetes RBAC.
Data handling: Reads/changes cluster resources.
Cost: unknown
Risk and cautions: Cluster-control authority can be very broad; use narrow RBAC and dedicated kubeconfigs.

Access scope and cautions

Write actions: Apply Create Patch Scale Restart Delete Copy Label
Sensitive access: Cluster state Potential secrets/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: Inspect cluster state; Apply/patch/scale/restart/delete resources; Diagnose networking/DNS; Query usage.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y kubectl-mcp-server. Recorded endpoint: http://127.0.0.1:8000. Recorded transport: stdio, sse, streamable_http. Prerequisites: kubectl; Node 14+ or Python 3.9+. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local kubeconfig context.

Can it modify data or perform write operations?

Documented write actions include: Apply; Create; Patch; Scale; Restart; Delete; Copy; Label. Recorded permission boundary: Kubernetes RBAC.

What data-handling boundary should I consider?

Reads/changes cluster resources. Recorded sensitive-access context: Cluster state; Potential secrets/workloads.

What limitations and risks should I check before use?

Cluster-control authority can be very broad; use narrow RBAC and dedicated kubeconfigs. Many destructive tools. Authority is inherited from kubeconfig/RBAC. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

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