Loading...
{
"mcpServers": {
"kom": {
"type": "sse",
"url": "http://IP:9096/sse"
}
}
}list_k8s_clustersLists all registered Kubernetes clusters.
Read-only operation, no side effects.
restart_k8s_daemonsetRestarts a Kubernetes DaemonSet.
Restarts a DaemonSet, causing temporary disruption.
scale_k8s_deploymentScales a Kubernetes Deployment by setting the replica count.
Modifies the number of replicas, potentially impacting application availability.
get_k8s_resourceRetrieves details of a Kubernetes resource.
Read-only operation, no side effects.
delete_k8s_resourceDeletes a Kubernetes resource.
Deletes a resource, causing permanent data loss or service disruption.
run_command_in_k8s_podExecutes a command inside a Kubernetes Pod.
Allows arbitrary command execution within a pod, potentially compromising the container.
delete_pod_fileDeletes a file within a Kubernetes Pod.
Deletes files within a pod, potentially disrupting the application.
taint_k8s_nodeAdds a taint to a Kubernetes node.
Modifies node scheduling behavior, potentially impacting workload distribution.
apply_k8s_yamlCreates or updates Kubernetes resources using a YAML file.
Applies changes defined in a YAML file, potentially modifying cluster state.
Kom provides a wide array of Kubernetes management tools, but its safety varies greatly depending on the specific tool used. Read-only operations are generally safe, while tools that modify or delete resources, or execute commands in pods, pose a higher risk. Proper RBAC and network security are crucial when exposing Kom via MCP.