Connections & Capabilities
Connects To
Capabilities
Quickstart
Config
{
"mcpServers": {
"mcp-k8s": {
"url": "http://localhost:8080/sse",
"args": []
}
}
}Exposed MCP Tools (14)
get_api_resourcesRetrieves all supported API resource types in the Kubernetes cluster.
Read-only operation, no modification of resources.
get_resourceRetrieves detailed information about a specific Kubernetes resource.
Read-only operation, no modification of resources.
list_resourcesLists all instances of a specific Kubernetes resource type.
Read-only operation, no modification of resources.
create_resourceCreates a new Kubernetes resource.
Adds new resources to the cluster.
update_resourceUpdates an existing Kubernetes resource.
Modifies existing resources, potentially disrupting services.
delete_resourceDeletes a Kubernetes resource.
Removes resources from the cluster, potentially causing downtime.
list_helm_releasesLists all Helm releases in the Kubernetes cluster.
Read-only operation, no modification of resources.
get_helm_releaseRetrieves detailed information about a specific Helm release.
Read-only operation, no modification of resources.
install_helm_chartInstalls a Helm chart into the Kubernetes cluster.
Deploys new applications, potentially impacting cluster resources.
upgrade_helm_chartUpgrades an existing Helm release.
Modifies existing deployments, potentially disrupting services.
uninstall_helm_chartUninstalls a Helm release from the Kubernetes cluster.
Removes deployments, potentially causing downtime.
list_helm_repositoriesLists all configured Helm repositories.
Read-only operation, no modification of resources.
add_helm_repositoryAdds a new Helm repository.
Adds a new source for Helm charts.
remove_helm_repositoryRemoves a Helm repository.
Removes a source for Helm charts.
Safety Assessment
mcp-k8s is relatively safe in read-only mode. Enabling write operations increases the risk, requiring careful configuration and monitoring. Using stdio mode is safer than exposing the server via HTTP.
- Fine-grained control over Kubernetes resource operations via flags.
- Write operations (create, update, delete) can be independently enabled/disabled.
- Uses RBAC to limit K8s client permissions.
- Input validation helps prevent injection attacks.
- If write operations are enabled, the server can modify Kubernetes resources.
- Kubeconfig file must be securely managed to prevent unauthorized access.
- Exposure via SSE or streamable HTTP increases the attack surface.
- Lack of built-in sandboxing for operations.
