MCP Server: Simplified Kubernetes Deployments & Governance

Mirror your Kubernetes ecosystems effortlessly – MCP Server offers seamless deployment, scaling, and governance for modern apps, turning complexity into simplicity. Deploy confidently.

Visit Repository

✨ Cloud Platforms

4.5(32 reviews)

48 saves

22 comments

86% of users reported increased productivity after just one week

About MCP Server

What is MCP Server: Simplified Kubernetes Deployments & Governance?

MCP Server is a tool designed to streamline interaction with Kubernetes clusters, enabling developers and operators to manage deployments, pods, services, and namespaces through a unified interface. By leveraging existing kubectl configurations, it automates cluster discovery and simplifies common tasks without requiring manual credential management. The server acts as a bridge between user commands and cluster operations, prioritizing ease-of-use while maintaining core Kubernetes governance workflows.

How to use MCP Server: Simplified Kubernetes Deployments & Governance?

To utilize MCP Server with tools like Claude Desktop, configure your environment as follows:

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

Ensure prerequisites are met: kubectl must be installed, configured with valid kubeconfig contexts, and have access to your target cluster (e.g., Minikube or GKE). Verify connectivity by issuing commands like list pods or create deployment. If errors occur, troubleshoot via terminal with kubectl get pods to isolate configuration issues.

MCP Server Features

Key Features of MCP Server: Simplified Kubernetes Deployments & Governance?

Core capabilities include:

Cluster Agnosticism: Works with any kubectl-accessible cluster (public clouds, self-hosted).
Resource Management: List/modify pods, deployments, and services across namespaces. Create/delete pods programmatically.
Namespace Awareness: Contextual namespace selection (planned enhancement).
Future Enhancements: Planned support for Helm charts and automated log retrieval.

Current limitations include pending implementations for port-forwarding and log streaming, which will address advanced debugging scenarios.

Use cases of MCP Server: Simplified Kubernetes Deployments & Governance?

Common scenarios include:

Rapid Prototyping: Developers can quickly spin up/test deployments without CLI navigation.
Automated Workflows: Integrate with chatbots or automation tools for repeatable cluster operations.
Multi-Cluster Governance: Manage multiple clusters via existing kubectx configurations (manual context switching required).
Debugging Aids: Identify pod statuses at a glance; planned log access will enhance troubleshooting.

For example, a team might use it to deploy a test NGINX instance with a single command: create deployment --image=nginx --name=test-nginx

MCP Server FAQ

FAQ from MCP Server: Simplified Kubernetes Deployments & Governance?

Q: Does MCP Server require additional authentication?
A: No. It relies on existing kubectl credentials stored in ~/.kube/config. Ensure your active context has sufficient permissions.
Q: Why can't I port-forward?
A: Port-forwarding support is under development. Current workaround: Use native kubectl port-forward commands.
Q: How do I contribute?
A: Fork the repository here. Tests are run via bun test; see the development section in docs for setup.
Q: Will it support cluster registration?
A: Authentication/cluster addition features are explicitly not planned. Users must manage contexts via kubectx or manual configuration.

Content

mcp-server-kubernetes

MCP Server that can connect to a Kubernetes cluster and manage it.

https://github.com/user-attachments/assets/f25f8f4e-4d04-479b-9ae0-5dac452dd2ed

Usage with Claude Desktop

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

The server will automatically connect to your current kubectl context. Make sure you have:

kubectl installed and in your PATH
A valid kubeconfig file with contexts configured
Access to a Kubernetes cluster configured for kubectl (e.g. minikube, Rancher Desktop, GKE, etc.)

You can verify your connection by asking Claude to list your pods or create a test deployment.

If you have errors, open up a standard terminal and run kubectl get pods to see if you can connect to your cluster without credentials issues.

Features

Connect to a Kubernetes cluster
List all pods
List all services
List all deployments
Create a pod
Delete a pod
List all namespaces
[] Port forward to a pod
[] Get logs from a pod for debugging
[] Choose namespace for next commands (memory)
[] Support Helm for installing charts

Development & Testing

git clone https://github.com/Flux159/mcp-server-kubernetes.git
cd mcp-server-kubernetes
bun install
bun run test

Not planned

Authentication / adding clusters to kubectx.