K8s Lens
Let your agent inspect and change Kubernetes resources across one or many clusters using plain language instead of memorizing kubectl for every incident.
Overview
K8s Lens MCP is an Operate-phase MCP server that runs natural-language Kubernetes operations across single or multi-cluster environments over stdio.
What is this MCP server?
- Natural-language Kubernetes operations across single or multi-cluster setups
- PyPI package k8s-lens-mcp 0.1.0 with stdio transport
- KUBECONFIG filepath env (defaults to ~/.kube/config)
- Optional OpenTelemetry OTLP endpoint for tracing
- MCP integration aimed at Lens-style operational visibility via agents
- Server version 0.1.0
- PyPI identifier k8s-lens-mcp at package version 0.1.0
- Transport: stdio
What problem does it solve?
Running kubectl across contexts and clusters from chat means context switches, typo-prone commands, and slow incident response for a solo operator.
Who is it for?
Indie builders or tiny teams operating real K8s clusters who want agent-assisted diagnostics and changes with existing kubeconfig access.
Skip if: Beginners still learning local Docker workflows or teams that forbid agent-driven changes against production RBAC.
What do I get? / Deliverables
After registration with a valid kubeconfig, your agent can query and act on cluster resources in natural language during infra and incident work.
- Agent-driven Kubernetes reads and operations aligned to your contexts
- Reduced friction for multi-cluster checks during incidents
- Optional OTLP tracing hook when OTEL_EXPORTER_OTLP_ENDPOINT is set
Recommended MCP Servers
Journey fit
Day-two cluster operations, debugging, and infra changes map to Operate once the product is already running in Kubernetes. Infra is the right shelf for multi-cluster context, kubeconfig-driven access, and operational commands—not initial app scaffolding in Build.
How it compares
Cluster operations MCP backed by kubeconfig, not a Terraform planning skill or local-only devcontainer setup guide.
Common Questions / FAQ
Who is K8s Lens MCP for?
Solo builders and small teams operating Kubernetes who use Claude Code or Cursor and want natural-language cluster queries and changes.
When should I use K8s Lens MCP?
Use it in Operate infra work when debugging deployments, comparing namespaces or clusters, or applying scoped changes you would otherwise type as kubectl.
How do I add K8s Lens MCP to my agent?
Install k8s-lens-mcp from PyPI, set KUBECONFIG to your kubeconfig path if not using the default, add the stdio MCP server entry, and restart the agent.