mcp-server-kubernetes
Connects to a Kubernetes cluster using the current kubectl context and provides tools to manage cluster resources, including listing pods, services, deployments, nodes, and namespaces; creating, deleting, and describing pods; and retrieving logs from pods, deployments, jobs, and label selectors.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-kubernetes list all pods running in my current Kubernetes cluster"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: mcp-server-kubernetes
Features
Connect to a Kubernetes cluster
List all pods
List all services
List all deployments
List all nodes
Create a pod
Delete a pod
Describe a pod
List all namespaces
Get logs from a pod for debugging (supports pods, deployments, jobs, and label selectors)
Port forward to a pod
Choose namespace for next commands (memory)
Support Helm for installing charts
Local Development
git clone https://github.com/Flux159/mcp-server-kubernetes.git
cd mcp-server-kubernetes
bun installDevelopment Workflow
Start the server in development mode (watches for file changes):
bun run devRun unit tests:
bun run testBuild the project:
bun run buildLocal Testing with Inspector
npx @modelcontextprotocol/inspector node build/index.js
# Follow further instructions on terminal for Inspector linkProject Structure
src/
├── index.ts # Main server implementation
├── types.ts # TypeScript type definitions
└── unit.test.ts # Unit testsContributing
Fork the repository
Create a feature branch
Make your changes
Add tests for new functionality
Ensure all tests pass
Submit a pull request
For bigger changes, please open an issue first to discuss the proposed changes.
Architecture
This section describes the high-level architecture of the MCP Kubernetes server.
Request Flow
The sequence diagram below illustrates how requests flow through the system:
sequenceDiagram
participant Client
participant Transport as StdioTransport
participant Server as MCP Server
participant Handler as Request Handler
participant K8sManager as KubernetesManager
participant K8s as Kubernetes API
Client->>Transport: Send Request via STDIO
Transport->>Server: Forward Request
alt Tools Request
Server->>Handler: Route to tools handler
Handler->>K8sManager: Execute tool operation
K8sManager->>K8s: Make API call
K8s-->>K8sManager: Return result
K8sManager-->>Handler: Process response
Handler-->>Server: Return tool result
else Resource Request
Server->>Handler: Route to resource handler
Handler->>K8sManager: Get resource data
K8sManager->>K8s: Query API
K8s-->>K8sManager: Return data
K8sManager-->>Handler: Format response
Handler-->>Server: Return resource data
end
Server-->>Transport: Send Response
Transport-->>Client: Return Final ResponseNot planned
Authentication / adding clusters to kubectx.
Available Tools
11 toolscleanupC
Cleanup all managed resources
Inputs: no named parameters.
create_deploymentC
Create a new Kubernetes deployment
Inputs: name (required), template (required), namespace (required), ports, +1 more.
create_podC
Create a new Kubernetes pod
Inputs: name (required), template (required), namespace (required), command.
delete_podC
Delete a Kubernetes pod
Inputs: name (required), namespace (required), ignoreNotFound.
describe_podB
Describe a Kubernetes pod (read details like status, containers, etc.)
Inputs: name (required), namespace (required).
get_logsC
Get logs from pods, deployments, jobs, or resources matching a label selector
Inputs: resourceType (required), name, tail, since, +4 more.
list_deploymentsC
List deployments in a namespace
Inputs: namespace (required).
list_namespacesB
List all namespaces
Inputs: no named parameters.
list_nodesB
List all nodes in the cluster
Inputs: no named parameters.
list_podsC
List pods in a namespace
Inputs: namespace (required).
list_servicesB
List services in a namespace
Inputs: namespace (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Most tools target clearly distinct Kubernetes resources and actions, such as list_pods vs list_deployments vs create_pod. The only mild ambiguity is cleanup, which could overlap conceptually with delete_pod if 'managed resources' includes pods created by the server.
The set mostly follows a predictable verb_noun pattern: list_pods, create_pod, delete_pod, describe_pod, get_logs. cleanup is the main deviation because it uses a single vague verb without a resource noun.
With 11 tools, the server is well-scoped for common Kubernetes inspection and basic pod/deployment operations. Each tool has a reasonably clear place and the count is neither thin nor bloated.
The surface covers listing core resources, creating pods/deployments, deleting pods, describing pods, logs, and cleanup. However, it lacks obvious lifecycle operations such as deleting deployments/services, updating or scaling deployments, and describing deployments/services, which limits common Kubernetes workflows.
Maintenance
Related MCP Connectors
The Google GKE MCP server is a managed Model Context Protocol server that provides AI applications with tools to manage Google Kubernetes Engine (GKE) clusters and Kubernetes resources. It exposes a structured, discoverable interface that allows AI agents to interact with GKE and Kubernetes APIs, enabling them to inspect cluster configurations, retrieve Kubernetes resource YAMLs, monitor operations like cluster upgrades, diagnose issues, and optimize costs—all without needing to parse text output or use complex kubectl commands.
Deploy applications and manage governed Kubernetes preview spaces and capacity.
Deploy and run apps, workers, jobs, Postgres, and Valkey on Ownkube from your coding agent.
Manage Kubernetes clusters, deployments, databases, secrets and observability on Mengi Cloud.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables connecting to a Kubernetes cluster to manage resources and troubleshoot workloads with kubectl and Helm operations, including logs, scaling, port forwarding, and non-destructive mode.2224,117 npmMIT
- AlicenseBqualityDmaintenanceEnables connection to a Kubernetes cluster to list and manage pods, services, deployments, and nodes, create/delete/describe pods, inspect namespaces, and retrieve logs for debugging.1124,117 npmMIT
- AlicenseBqualityDmaintenanceEnables connecting to a Kubernetes cluster to manage it, including listing pods, services, deployments, nodes, and namespaces, creating and deleting pods, describing pods, and retrieving logs for debugging.1124,117 npmMIT
- AlicenseBqualityDmaintenanceConnects to a Kubernetes cluster through the current kubectl context and enables listing, creating, deleting, and describing pods, services, deployments, nodes, and namespaces, plus retrieving logs for debugging.1124,117 npmMIT