mcp-server-k8s-go
Provides an MCP server (stdio transport) intended to interact with Kubernetes using Go. The README shows how to run it for local testing and how to configure it as a local MCP server (with KUBECONFIG) in clients like Cline.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
The interface (stdio MCP) suggests no network transport/TLS concerns from the README alone, but the server likely operates with kubeconfig-derived credentials. Security therefore depends heavily on least-privilege Kubernetes RBAC and protecting the kubeconfig. README does not mention RBAC hardening, auditing, or safe operation constraints, and provides no guidance on how secrets are handled/logged by the server.
⚡ Reliability
Best When
You have a local or controlled Kubernetes environment (e.g., minikube) and want an MCP bridge for experimentation or internal tooling.
Avoid When
You need strict operational safety controls (RBAC scoping, auditability, approval workflows) or you cannot manage kubeconfig permissions securely.
Use Cases
- • Kubernetes cluster inspection and operations via MCP tooling (e.g., prompts that trigger kubectl-like actions)
- • Local dev/testing of MCP agents that need access to Kubernetes resources
- • Hands-on experimentation with Model Context Protocol servers and the stdio transport
Not For
- • Production-grade cluster automation without additional security hardening
- • Use cases requiring robust, documented CRUD semantics, pagination, or formal API contracts beyond the MCP interface
- • Environments where agents must not have access to kubeconfig-derived credentials
Interface
Authentication
No explicit auth mechanism is described in the README beyond using a kubeconfig path via env. Actual authorization is therefore governed by the kubeconfig credentials and Kubernetes RBAC.
Pricing
No pricing information provided (repo appears to be open source).
Agent Metadata
Known Gotchas
- ⚠ MCP communication is via stdio; agents/tools must correctly wire stdin/stdout transport.
- ⚠ The README provides only high-level usage; the available MCP tools/resources and their parameter schemas are not shown here.
- ⚠ KUBECONFIG is passed via env; agents may accidentally target the wrong cluster/context if kubeconfig is misconfigured.
- ⚠ No rate-limit, timeout, or retry guidance is documented, so agents may need conservative timeouts and manual retries if supported by the implementation.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-k8s-go.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.