Loading...
mcp-k8s-eye provides comprehensive Kubernetes cluster management and diagnostics, including resource operations, analysis, and monitoring via multiple transport protocols.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
mcp-k8s-eye provides comprehensive Kubernetes cluster management and diagnostics, including resource operations, analysis, and monitoring via multiple transport protocols.
mcp-k8s-eye offers powerful Kubernetes management capabilities, but the ability to create, update, delete resources and execute commands in pods introduces risk. It is safe to use for monitoring and diagnostics in read-only mode. Exercise caution when using write operations, especially in production environments.
Performance depends on the size and complexity of the Kubernetes cluster. Large clusters may experience slower response times.
Cost is primarily related to the resources consumed by the mcp-k8s-eye server itself. There are no direct API call costs associated with Kubernetes operations.
{
"mcpServers": {
"k8s eye": {
"command": "YOUR mcp-k8s-eye PATH",
"env": {
"HOME": "USER HOME DIR"
},
}
}
}resource_getRetrieves detailed information about a specific Kubernetes resource.
Read-only operation, no modification of resources.
resource_listLists detailed information about all Kubernetes resources in a namespace.
Read-only operation, no modification of resources.
resource_create_or_updateCreates or updates a Kubernetes resource in a specified namespace.
Modifies cluster state, potentially causing disruption or security issues.
resource_deleteDeletes a Kubernetes resource from a specified namespace.
Destructive operation that can lead to data loss or service disruption.
resource_describeProvides detailed information about a Kubernetes resource.
Read-only operation, no modification of resources.
deployment_scaleScales a Kubernetes deployment in a specified namespace.
Modifies the number of replicas, potentially impacting application availability.
pod_execExecutes a command within a pod in a specified namespace.
Allows arbitrary command execution within a container, posing a significant security risk.
pod_logsRetrieves logs from a pod in a specified namespace.
Read-only operation, no modification of resources.
pod_analyzeDiagnoses all pods in a namespace, identifying potential issues.
Read-only analysis of pod status.
deployment_analyzeDiagnoses all deployments in a namespace, identifying potential issues.
Read-only analysis of deployment status.
statefulset_analyzeDiagnoses all statefulsets in a namespace, identifying potential issues.
Read-only analysis of statefulset status.
service_analyzeDiagnoses all services in a namespace, identifying potential issues.
Read-only analysis of service configuration and endpoints.
cronjob_analyzeDiagnoses all cronjobs in a namespace, identifying potential issues.
Read-only analysis of cronjob schedule and status.
ingress_analyzeDiagnoses all ingresses in a namespace, identifying potential issues.
Read-only analysis of ingress configuration and related services.
networkpolicy_analyzeDiagnoses all networkpolicies in a namespace, identifying potential issues.
Read-only analysis of networkpolicy configuration and affected pods.
validatingwebhook_analyzeDiagnoses all validating webhooks, identifying potential issues.
Read-only analysis of validating webhook configurations.
mutatingwebhook_analyzeDiagnoses all mutating webhooks, identifying potential issues.
Read-only analysis of mutating webhook configurations.
node_analyzeDiagnoses all nodes in the cluster, identifying potential issues.
Read-only analysis of node conditions.
workload_resource_usageGets pod/deployment/replicaset/statefulset resource usage in a namespace (cpu, memory).
Read-only operation, no modification of resources.
Environment Variable
hybrid
mcp-k8s-eye offers powerful Kubernetes management capabilities, but the ability to create, update, delete resources and execute commands in pods introduces risk. It is safe to use for monitoring and diagnostics in read-only mode. Exercise caution when using write operations, especially in production environments.
Autonomy is highly dependent on the specific tool used. Read-only tools are safe for automated use, while write operations require careful consideration and validation.
Production Tip
Use caution when automating write operations, especially in production. Implement thorough validation and testing before deploying changes.
The tool supports all native Kubernetes resources (Pod, Deployment, Service, etc.) and CustomResourceDefinitions.
The tool relies on a properly configured kubectl environment. Ensure your kubeconfig file is set up correctly.
You can manage multiple clusters by configuring multiple kubectl contexts and switching between them as needed.
Yes, the tool respects RBAC settings configured in your Kubernetes cluster. Ensure the user or service account running the tool has the necessary permissions.
Use the `workload_resource_usage` tool to get CPU and memory usage for pods, deployments, replicasets, and statefulsets.
The tool does not have a built-in dry-run mode. You should carefully review the changes before applying them.
The tool supports Stdio and SSE transport protocols.