MCP Server for kubernetes management and diagnose your cluster and applications
Connect MCP K8s Eye to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP Server for kubernetes management and diagnose your cluster and applications. The mcp k8s eye mcp server is what makes that connection.
mcp-k8s-eye is a tool that can manage kubernetes cluster and analyze workload status.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
resource_get — Get detailed resource information about a specific resource in a namespaceresource_list — List detailed resource information about all resources in a namespaceresource_create_or_update — Create or update a resource in a namespaceresource_delete — Delete a resource in a namespaceresource_describe — Describe a resource detailed information in a namespacedeployment_scale — Scale a deployment in a namespacepod_exec — Execute a command in a pod in a namespacepod_logs — Get logs from a pod in a namespacepod_analyze — Diagnose all pods in a namespacedeployment_analyze — Diagnose all deployments in a namespacestatefulset_analyze — Diagnose all statefulsets in a namespaceservice_analyze — Diagnose all services in a namespaceSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP K8s Eye's toolset — resource_get, resource_list, resource_create_or_update and 11 more — is a fair guide to whether it matches your workflow. It is maintained by wenhuwang; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP K8s Eye's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| resource_get | Get detailed resource information about a specific resource in a namespace |
| resource_list | List detailed resource information about all resources in a namespace |
| resource_create_or_update | Create or update a resource in a namespace |
| resource_delete | Delete a resource in a namespace |
| resource_describe | Describe a resource detailed information in a namespace |
| deployment_scale | Scale a deployment in a namespace |
| pod_exec | Execute a command in a pod in a namespace |
| pod_logs | Get logs from a pod in a namespace |
| pod_analyze | Diagnose all pods in a namespace |
| deployment_analyze | Diagnose all deployments in a namespace |
| statefulset_analyze | Diagnose all statefulsets in a namespace |
| service_analyze | Diagnose all services in a namespace |
| cronjob_analyze | Diagnose all cronjobs in a namespace |
| ingress_analyze | Diagnose all ingresses in a namespace |
{
"mcpServers": {
"k8s eye": {
"command": "YOUR mcp-k8s-eye PATH",
"env": {
"HOME": "USER HOME DIR"
},
}
}
}Configuration as documented by the project. Restart the client after saving.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.