Loading...
mcp-k8s provides a Model Control Protocol server for managing Kubernetes resources and Helm deployments via standard I/O, SSE, or streamable HTTP.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
mcp-k8s provides a Model Control Protocol server for managing Kubernetes resources and Helm deployments via standard I/O, SSE, or streamable HTTP.
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.
Performance depends on the size of the Kubernetes cluster and the complexity of the operations. Network latency can impact performance in SSE and streamable HTTP modes.
Cost depends on the underlying Kubernetes resources managed by mcp-k8s. There are no direct costs associated with mcp-k8s itself.
{
"mcpServers": {
"mcp-k8s": {
"url": "http://localhost:8080/sse",
"args": []
}
}
}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.
Token
hybrid
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.
Autonomy depends on the enabled tools and the permissions granted to the K8s client. Exercise caution when enabling write operations.
Production Tip
Monitor the mcp-k8s server logs and Kubernetes audit logs for any suspicious activity.
mcp-k8s is an MCP server that allows you to manage Kubernetes resources and Helm deployments using natural language commands.
mcp-k8s supports stdio, SSE (Server-Sent Events), and streamable HTTP modes.
You can enable write operations by using the `--enable-create`, `--enable-update`, and `--enable-delete` flags when starting the server.
mcp-k8s includes security features like RBAC and input validation, but it's crucial to configure it properly and monitor its activity.
Both SSE and streamable HTTP expose an HTTP endpoint, but streamable HTTP supports both direct HTTP responses and SSE streams, providing more flexibility.
Refer to your MCP client's documentation for integration instructions. mcp-k8s is an stdio-based MCP server that can be integrated with any MCP-compatible LLM client.
The required permissions depend on the enabled tools. Read-only operations require minimal permissions, while write operations require permissions to create, update, and delete resources.