Kubernetes MCP Server
✨ Features | 🚀 Getting Started | 🎥 Demos | ⚙️ Configuration | 🛠️ Tools | 💬 Community | 🧑💻 Development
https://github.com/user-attachments/assets/be2b67b3-fc1c-4d11-ae46-93deba8ed98e
✨ Features
A powerful and flexible Kubernetes Model Context Protocol (MCP) server implementation with support for Kubernetes and OpenShift.
- ✅ Configuration:
- Automatically detect changes in the Kubernetes configuration and update the MCP server.
- View and manage the current Kubernetes
.kube/config or in-cluster configuration.
- ✅ Generic Kubernetes Resources: Perform operations on any Kubernetes or OpenShift resource.
- Any CRUD operation (Create or Update, Get, List, Delete).
- ✅ Pods: Perform Pod-specific operations.
- List pods in all namespaces or in a specific namespace.
- Get a pod by name from the specified namespace.
- Delete a pod by name from the specified namespace.
- Show logs for a pod by name from the specified namespace.
- Top gets resource usage metrics for all pods or a specific pod in the specified namespace.
- Exec into a pod and run a command.
- Run a container image in a pod and optionally expose it.
- ✅ Namespaces: List Kubernetes Namespaces.
- ✅ Events: View Kubernetes events in all namespaces or in a specific namespace.
- ✅ Projects: List OpenShift Projects.
- ☸️ Helm:
- Install a Helm chart in the current or provided namespace.
- List Helm releases in all namespaces or in a specific namespace.
- Uninstall a Helm release in the current or provided namespace.
- 🔧 Tekton: Tekton-specific operations that complement generic Kubernetes resource management.
- Pipeline: Start a Tekton Pipeline by creating a PipelineRun.
- PipelineRun: Restart, cancel, troubleshoot, and retrieve PipelineRun logs.
- Task: Start a Tekton Task by creating a TaskRun.
- TaskRun: Restart a TaskRun with the same spec, and retrieve TaskRun logs via pod resolution.
- 🔭 Observability: Optional OpenTelemetry distributed tracing and metrics with custom sampling rates. Includes
/stats endpoint for real-time statistics. See OTEL.md.
Unlike other Kubernetes MCP server implementations, this IS NOT just a wrapper around kubectl or helm command-line tools.
It is a Go-based native implementation that interacts directly with the Kubernetes API server.
There is NO NEED for external dependencies or tools to be installed on the system.
If you're using the native binaries you don't need to have Node or Python installed on your system.
- ✅ Lightweight: The server is distributed as a single native binary for Linux, macOS, and Windows.
- ✅ High-Performance / Low-Latency: Directly interacts with the Kubernetes API server without the overhead of calling and waiting for external commands.
- ✅ Multi-Cluster: Can interact with multiple Kubernetes clusters simultaneously (as defined in your kubeconfig files).
- ✅ Cross-Platform: Available as a native binary for Linux, macOS, and Windows, as well as an npm package, a Python package, and container/Docker image.
- ✅ Configurable: Supports command-line arguments, TOML configuration files, and environment variables.
- ✅ Well tested: The server has an extensive test suite to ensure its reliability and correctness across different Kubernetes environments.
- 📚 Documentation: Comprehensive user documentation including setup guides, configuration reference, and observability.
🎥 Demos
Diagnosing and automatically fixing an OpenShift Deployment
Demo showcasing how Kubernetes MCP server is leveraged by Claude Desktop to automatically diagnose and fix a deployment in OpenShift without any user assistance.
https://github.com/user-attachments/assets/a576176d-a142-4c19-b9aa-a83dc4b8d941
Vibe Coding a simple game and deploying it to OpenShift
In this demo, I walk you through the process of Vibe Coding a simple game using VS Code and how to leverage Podman MCP server and Kubernetes MCP server to deploy it to OpenShift.
⚙️ Configuration
The Kubernetes MCP server can be configured using command line (CLI) arguments.
You can run the CLI executable either by using npx, uvx, or by downloading the latest release binary.
# Run the Kubernetes MCP server using npx (in case you have npm and node installed)
npx kubernetes-mcp-server@latest --help
# Run the Kubernetes MCP server using uvx (in case you have uv and python installed)
uvx kubernetes-mcp-server@latest --help
# Run the Kubernetes MCP server using the latest release binary
./kubernetes-mcp-server --help
Configuration Options
| Option | Description |
|---|
--version | Print version information and quit. |
--config | Path to the main TOML configuration file. See Configuration Reference for all options (port, toolsets, read_only, kubeconfig, …). |
--config-dir | Directory of lexical .toml files. Usable alone or with --config. Omitted means no drop-ins. Relative paths are resolved against the working directory. |
Note: Runtime settings are TOML (or existing env names), not CLI flags. See Configuration Changes for the flag-to-TOML mapping.
TOML Configuration Files
For complex or persistent configurations, use TOML configuration files instead of CLI arguments:
kubernetes-mcp-server --config /etc/kubernetes-mcp-server/config.toml
Example configuration:
log_level = 2
read_only = true
toolsets = ["core", "config", "helm", "kubevirt"]
# Deny access to sensitive resources
[[denied_resources]]
group = ""
version = "v1"
kind = "Secret"
[telemetry]
endpoint = "http://localhost:4317"
For comprehensive TOML configuration documentation, including:
- All configuration options and their defaults
- Drop-in configuration files for modular settings
- Dynamic configuration reload via SIGHUP
- Denied resources for restricting access to sensitive resource types
- Server instructions for MCP Tool Search
- Custom MCP prompts
- OAuth/OIDC authentication for HTTP mode (Keycloak, Microsoft Entra ID)
See the Configuration Reference.
📊 MCP Logging
The server supports the MCP logging capability, allowing clients to receive debugging information via structured log messages.
Kubernetes API errors are automatically categorized and logged to clients with appropriate severity levels.
Sensitive data (tokens, keys, passwords, cloud credentials) is automatically redacted before being sent to clients.
See the MCP Logging Guide.
🛠️ Tools and Functionalities
The Kubernetes MCP server supports enabling or disabling specific groups of tools and functionalities (tools, resources, prompts, and so on) via the toolsets configuration option.
This allows you to control which Kubernetes functionalities are available to your AI tools.
Enabling only the toolsets you need can help reduce the context size and improve the LLM's tool selection accuracy.
Validated Kubernetes Ecosystem Projects
The following CNCF and Kubernetes ecosystem projects are covered by
automated evaluation scenarios in evals/tasks. Most scenarios
work with just the core toolset. The dedicated toolsets below are optional
and only needed for the project-specific scenarios noted.
Available Toolsets
The following sets of tools are available (toolsets marked with ✓ in the Default column are enabled by default):
| Toolset | Description | Default |
|---|
| config | View and manage the current local Kubernetes configuration (kubeconfig) | ✓ |
| core | Most common tools for Kubernetes management (Pods, Generic Resources, Events, etc.) | ✓ |
| helm | Tools for managing Helm charts and releases | |
| kcp | Manage kcp workspaces and multi-tenancy features | |
| kiali | Most common tools for managing Kiali, check the Kiali documentation for more details. | |
| kubevirt | KubeVirt virtual machine management tools, check the KubeVirt documentation for more details. | |
| netobserv | Network observability tools backed by the NetObserv console plugin API (flows, metrics, export). Check the NetObserv documentation for more details. | |
| observability/logs | Toolset for querying Loki logs | |
| observability/metrics | Toolset for querying Prometheus and Alertmanager endpoints in efficient ways. | |
| observability/otelcol | Toolset for OpenTelemetry Collector configuration assistance including schema validation, component documentation, and version management. | |
| observability/traces | Distributed tracing tools for discovering Tempo instances, searching and retrieving traces, and exploring trace attributes. | |
| tekton | Tekton pipeline management tools for Pipelines, PipelineRuns, Tasks, TaskRuns, and troubleshooting. | |
Tools
In case multi-cluster support is enabled (default) and you have access to multiple clusters, all applicable tools will include an additional context argument to specify the Kubernetes context (cluster) to use for that operation.
-
configuration_contexts_list - List all available context names and associated server urls from the kubeconfig file
-
targets_list - List all available targets
-
configuration_view - Get the current Kubernetes configuration content as a kubeconfig YAML
minified (boolean) - Return a minified version of the configuration. If set to true, keeps only the current-context and the relevant pieces of the configuration for that context. If set to false, all contexts, clusters, auth-infos, and users are returned in the configuration. (Optional, default true)
-
events_list - List Kubernetes events (warnings, errors, state changes) for debugging and troubleshooting in the current cluster from all namespaces. Use limit and continue to retrieve a large list one page at a time.
continue (string) - Opaque token from the continue field of the previous page. Send it unchanged with the same limit, namespace, and selectors to retrieve the next page. Omit on the first call.fieldSelector (string) - Optional Kubernetes field selector to filter events by field values (e.g. 'type=Warning', 'involvedObject.name=my-pod'). Supported fields: involvedObject.kind, involvedObject.name, involvedObject.namespace, involvedObject.uid, involvedObject.apiVersion, involvedObject.resourceVersion, involvedObject.fieldPath, reason, reportingComponent, source, type. See https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/limit (integer) - Maximum number of items to return. Omit or set to 0 to list everything, which fails if the response exceeds max_backend_response_bytes. Retry with a smaller limit when that happens. The API may return fewer items than requested.namespace (string) - Optional Namespace to retrieve the events from. If not provided, will list events from all namespaces
-
namespaces_list - List all the Kubernetes namespaces in the current cluster. Use limit and continue to retrieve a large list one page at a time.
continue (string) - Opaque token from the continue field of the previous page. Send it unchanged with the same limit, namespace, and selectors to retrieve the next page. Omit on the first call.fieldSelector (string) - Optional Kubernetes field selector to filter namespaces by field values (e.g. 'metadata.name=default', 'status.phase=Active'). Supported fields: metadata.name, status.phase. See https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/limit (integer) - Maximum number of items to return. Omit or set to 0 to list everything, which fails if the response exceeds max_backend_response_bytes. Retry with a smaller limit when that happens. The API may return fewer items than requested.
-
projects_list - List all the OpenShift projects in the current cluster. Use limit and continue to retrieve a large list one page at a time.
continue (string) - Opaque token from the continue field of the previous page. Send it unchanged with the same limit, namespace, and selectors to retrieve the next page. Omit on the first call.limit (integer) - Maximum number of items to return. Omit or set to 0 to list everything, which fails if the response exceeds max_backend_response_bytes. Retry with a smaller limit when that happens. The API may return fewer items than requested.
-
nodes_log - Get logs from a Kubernetes node (kubelet, kube-proxy, or other system logs). This accesses node logs through the Kubernetes API proxy to the kubelet
name (string) (required) - Name of the node to get logs fromquery (string) (required) - query specifies services(s) or files from which to return logs (required). Example: "kubelet" to fetch kubelet logs, "/" to fetch a specific log file from the node (e.g., "/var/log/kubelet.log" or "/var/log/kube-proxy.log")tailLines (integer) - Number of lines to retrieve from the end of the logs (Optional, 0 means all logs)
-
nodes_stats_summary - Get detailed resource usage statistics from a Kubernetes node via the kubelet's Summary API. Provides comprehensive metrics including CPU, memory, filesystem, and network usage at the node, pod, and container levels. On systems with cgroup v2 and kernel 4.20+, also includes PSI (Pressure Stall Information) metrics that show resource pressure for CPU, memory, and I/O. See https://kubernetes.io/docs/reference/instrumentation/understand-psi-metrics/ for details on PSI metrics
name (string) (required) - Name of the node to get stats from
-
nodes_top - List the resource consumption (CPU and memory) as recorded by the Kubernetes Metrics Server for the specified Kubernetes Nodes or all nodes in the cluster. Use limit and continue to retrieve a large list one page at a time.
continue (string) - Opaque token from the continue field of the previous page. Send it unchanged with the same limit, namespace, and selectors to retrieve the next page. Omit on the first call.label_selector (string) - Kubernetes label selector (e.g. 'node-role.kubernetes.io/worker=') to filter nodes by label (Optional, only applicable when name is not provided)limit (integer) - Maximum number of items to return. Omit or set to 0 to list everything, which fails if the response exceeds max_backend_response_bytes. Retry with a smaller limit when that happens. The API may return fewer items than requested.name (string) - Name of the Node to get the resource consumption from (Optional, all Nodes if not provided)
-
pods_list - List all the Kubernetes pods in the current cluster from all namespaces. Use limit and continue to retrieve a large list one page at a time.
continue (string) - Opaque token from the continue field of the previous page. Send it unchanged with the same limit, namespace, and selectors to retrieve the next page. Omit on the first call.fieldSelector (string) - Optional Kubernetes field selector to filter pods by field values (e.g. 'status.phase=Running', 'spec.nodeName=node1'). Supported fields: metadata.name, metadata.namespace, spec.nodeName, spec.restartPolicy, spec.schedulerName, spec.serviceAccountName, status.phase (Pending/Running/Succeeded/Failed/Unknown), status.podIP, status.nominatedNodeName. Note: CrashLoopBackOff is a container state, not a pod phase, so it cannot be filtered directly. See https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/labelSelector (string) - Optional Kubernetes label selector (e.g. 'app=myapp,env=prod' or 'app in (myapp,yourapp)'), use this option when you want to filter the pods by labellimit (integer) - Maximum number of items to return. Omit or set to 0 to list everything, which fails if the response exceeds max_backend_response_bytes. Retry with a smaller limit when that happens. The API may return fewer items than requested.
-
pods_list_in_namespace - List all the Kubernetes pods in the specified namespace in the current cluster. Use limit and continue to retrieve a large list one page at a time.
continue (string) - Opaque token from the continue field of the previous page. Send it unchanged with the same limit, namespace, and selectors to retrieve the next page. Omit on the first call.fieldSelector (string) - Optional Kubernetes field selector to filter pods by field values (e.g. 'status.phase=Running', 'spec.nodeName=node1'). Supported fields: metadata.name, metadata.namespace, spec.nodeName, spec.restartPolicy, spec.schedulerName, spec.serviceAccountName, status.phase (Pending/Running/Succeeded/Failed/Unknown), status.podIP, status.nominatedNodeName. Note: CrashLoopBackOff is a container state, not a pod phase, so it cannot be filtered directly. See https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/labelSelector (string) - Optional Kubernetes label selector (e.g. 'app=myapp,env=prod' or 'app in (myapp,yourapp)'), use this option when you want to filter the pods by labellimit (integer) - Maximum number of items to return. Omit or set to 0 to list everything, which fails if the response exceeds max_backend_response_bytes. Retry with a smaller limit when that happens. The API may return fewer items than requested.namespace (string) (required) - Namespace to list pods from
-
pods_get - Get a Kubernetes Pod in the current or provided namespace with the provided name
name (string) (required) - Name of the Podnamespace (string) - Namespace to get the Pod from
-
pods_delete - Delete a Kubernetes Pod in the current or provided namespace with the provided name
name (string) (required) - Name of the Pod to deletenamespace (string) - Namespace to delete the Pod from
-
pods_top - List the resource consumption (CPU and memory) as recorded by the Kubernetes Metrics Server for the specified Kubernetes Pods in the all namespaces, the provided namespace, or the current namespace. Use limit and continue to retrieve a large list one page at a time.
all_namespaces (boolean) - If true, list the resource consumption for all Pods in all namespaces. If false, list the resource consumption for Pods in the provided namespace or the current namespacecontinue (string) - Opaque token from the continue field of the previous page. Send it unchanged with the same limit, namespace, and selectors to retrieve the next page. Omit on the first call.label_selector (string) - Kubernetes label selector (e.g. 'app=myapp,env=prod' or 'app in (myapp,yourapp)'), use this option when you want to filter the pods by label (Optional, only applicable when name is not provided)limit (integer) - Maximum number of items to return. Omit or set to 0 to list everything, which fails if the response exceeds max_backend_response_bytes. Retry with a smaller limit when that happens. The API may return fewer items than requested.name (string) - Name of the Pod to get the resource consumption from (Optional, all Pods in the namespace if not provided)namespace (string) - Namespace to get the Pods resource consumption from (Optional, current namespace if not provided and all_namespaces is false)
-
pods_exec - Execute a command in a Kubernetes Pod (shell access, run commands in container) in the current or provided namespace with the provided name and command
command (array) (required) - Command to execute in the Pod container. The first item is the command to be run, and the rest are the arguments to that command. Example: ["ls", "-l", "/tmp"]container (string) - Name of the Pod container where the command will be executed (Optional)name (string) (required) - Name of the Pod where the command will be executednamespace (string) - Namespace of the Pod where the command will be executed
-
pods_log - Get the logs of a Kubernetes Pod in the current or provided namespace with the provided name
container (string) - Name of the Pod container to get the logs from (Optional)name (string) (required) - Name of the Pod to get the logs fromnamespace (string) - Namespace to get the Pod logs fromprevious (boolean) - Return previous terminated container logs (Optional)tail (integer) - Number of lines to retrieve from the end of the logs (Optional, default: 100)
-
pods_run - Run a Kubernetes Pod in the current or provided namespace with the provided container image and optional name
image (string) (required) - Container Image to run in the Podname (string) - Name of the Pod (Optional, random name if not provided)namespace (string) - Namespace to run the Pod inport (number) - TCP/IP port to expose from the Pod container (Optional, no port exposed if not provided)
-
resources_list - List Kubernetes resources and objects in the current cluster by providing their apiVersion and kind and optionally the namespace and label selector. Use limit and continue to retrieve a large list one page at a time.
(common apiVersion and kind include: v1 Pod, v1 Service, v1 Node, apps/v1 Deployment, networking.k8s.io/v1 Ingress, route.openshift.io/v1 Route)
apiVersion (string) (required) - apiVersion of the resources (examples of valid apiVersion are: v1, apps/v1, networking.k8s.io/v1)continue (string) - Opaque token from the continue field of the previous page. Send it unchanged with the same limit, namespace, and selectors to retrieve the next page. Omit on the first call.fieldSelector (string) - Optional Kubernetes field selector to filter resources by field values (e.g. 'status.phase=Running', 'metadata.name=myresource'). Supported fields vary by resource type. For Pods: metadata.name, metadata.namespace, spec.nodeName, spec.restartPolicy, spec.schedulerName, spec.serviceAccountName, status.phase (Pending/Running/Succeeded/Failed/Unknown), status.podIP, status.nominatedNodeName. See https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/kind (string) (required) - kind of the resources (examples of valid kind are: Pod, Service, Deployment, Ingress)labelSelector (string) - Optional Kubernetes label selector (e.g. 'app=myapp,env=prod' or 'app in (myapp,yourapp)'), use this option when you want to filter the resources by labellimit (integer) - Maximum number of items to return. Omit or set to 0 to list everything, which fails if the response exceeds max_backend_response_bytes. Retry with a smaller limit when that happens. The API may return fewer items than requested.namespace (string) - Optional Namespace to retrieve the namespaced resources from (ignored in case of cluster scoped resources). If not provided, will list resources from all namespaces
-
resources_get - Get a Kubernetes resource in the current cluster by providing its apiVersion, kind, optionally the namespace, and its name
(common apiVersion and kind include: v1 Pod, v1 Service, v1 Node, apps/v1 Deployment, networking.k8s.io/v1 Ingress, route.openshift.io/v1 Route)
apiVersion (string) (required) - apiVersion of the resource (examples of valid apiVersion are: v1, apps/v1, networking.k8s.io/v1)kind (string) (required) - kind of the resource (examples of valid kind are: Pod, Service, Deployment, Ingress)name (string) (required) - Name of the resourcenamespace (string) - Optional Namespace to retrieve the namespaced resource from (ignored in case of cluster scoped resources). If not provided, will get resource from configured namespace
-
resources_create_or_update - Create or update a Kubernetes resource via Server-Side Apply. The manifest is the complete desired state: any field this tool previously set and the new manifest omits is removed. To edit an existing resource, fetch it with resources_get, modify it, then re-apply the full resource.
(common apiVersion and kind include: v1 Pod, v1 Service, v1 Node, apps/v1 Deployment, networking.k8s.io/v1 Ingress, route.openshift.io/v1 Route)
resource (string) (required) - Complete YAML or JSON representation of the Kubernetes resource (full desired state, not a partial patch). Include apiVersion, kind, metadata, and the full spec.
-
resources_delete - Delete a Kubernetes resource in the current cluster by providing its apiVersion, kind, optionally the namespace, and its name
(common apiVersion and kind include: v1 Pod, v1 Service, v1 Node, apps/v1 Deployment, networking.k8s.io/v1 Ingress, route.openshift.io/v1 Route)
apiVersion (string) (required) - apiVersion of the resource (examples of valid apiVersion are: v1, apps/v1, networking.k8s.io/v1)gracePeriodSeconds (integer) - Optional duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be usedkind (string) (required) - kind of the resource (examples of valid kind are: Pod, Service, Deployment, Ingress)name (string) (required) - Name of the resourcenamespace (string) - Optional Namespace to delete the namespaced resource from (ignored in case of cluster scoped resources). If not provided, will delete resource from configured namespace
-
resources_scale - Get or update the scale of a Kubernetes resource in the current cluster by providing its apiVersion, kind, name, and optionally the namespace. If the scale is set in the tool call, the scale will be updated to that value. Always returns the current scale of the resource
apiVersion (string) (required) - apiVersion of the resource (examples of valid apiVersion are apps/v1)kind (string) (required) - kind of the resource (examples of valid kind are: StatefulSet, Deployment)name (string) (required) - Name of the resourcenamespace (string) - Optional Namespace to get/update the namespaced resource scale from (ignored in case of cluster scoped resources). If not provided, will get/update resource scale from configured namespacescale (integer) - Optional scale to update the resources scale to. If not provided, will return the current scale of the resource, and not update it
-
helm_install - Install (deploy) a Helm chart to create a release in the current or provided namespace
chart (string) (required) - Chart reference to install (for example: stable/grafana, oci://ghcr.io/nginxinc/charts/nginx-ingress)name (string) - Name of the Helm release (Optional, random name if not provided)namespace (string) - Namespace to install the Helm chart in (Optional, current namespace if not provided)values (object) - Values to pass to the Helm chart (Optional)
-
helm_list - List all the Helm releases in the current or provided namespace (or in all namespaces if specified). Use limit and offset to page the releases returned to you. Helm loads release secrets before applying that page, so a secret list that exceeds max_backend_response_bytes can still fail.
all_namespaces (boolean) - If true, lists all Helm releases in all namespaces ignoring the namespace argument (Optional)limit (integer) - Maximum number of releases to return. Omit or set to 0 to return every release Helm loaded. A full page tells you the next offset.namespace (string) - Namespace to list Helm releases from (Optional, all namespaces if not provided)offset (integer) - Number of releases to skip. Send the next offset from a full page, with the same limit.
-
helm_uninstall - Uninstall a Helm release in the current or provided namespace
name (string) (required) - Name of the Helm release to uninstallnamespace (string) - Namespace to uninstall the Helm release from (Optional, current namespace if not provided)
-
kiali_get_mesh_traffic_graph - Returns service-to-service traffic topology, dependencies, and network metrics (throughput, response time, mTLS) for the specified namespaces. Use this to diagnose routing issues, latency, or find upstream/downstream dependencies.
graphType (string) - Granularity of the graph. 'app' aggregates by app name, 'versionedApp' separates by versions, 'workload' maps specific pods/deployments. Default: versionedApp.meshCluster (string) - Optional Istio mesh cluster name from kiali_list_mesh_clusters (e.g. west). When omitted, Kiali defaults to its home cluster.namespaces (string) (required) - Comma-separated list of namespaces to map
-
kiali_get_mesh_status - Retrieves the high-level health, topology, and environment details of the Istio service mesh. Returns multi-cluster control plane status (istiod), data plane namespace health (including ambient mesh status), observability stack health (Prometheus, Grafana...), and component connectivity. Use this tool as the first step to diagnose mesh-wide issues, verify Istio/Kiali versions, or check overall health before drilling into specific workloads.
-
kiali_manage_istio_config_read - Read Istio, Gateway API, and Inference API config. 'list' groups by namespace→'group/version/kind'→{valid:[...],invalid:[...]} where valid/invalid arrays contain resource names; omit group/kind to retrieve ALL config types in a single call. Supports Istio (networking.istio.io, security.istio.io), Gateway API (gateway.networking.k8s.io), and Inference API (inference.networking.k8s.io) when installed. 'get' returns full YAML. For writes use manage_istio_config.
action (string) (required) - Action to perform (read-only)group (string) - API group of the Istio object. Required ONLY for 'get' action. For 'list', OMIT group and kind to retrieve ALL config types in a single call. Use 'gateway.networking.k8s.io' for Gateway API resources. Use 'inference.networking.k8s.io' for Inference API resources.kind (string) - Kind of the Istio object. Required ONLY for 'get' action. For 'list', OMIT to return all kinds at once — do NOT call separately for each kind.meshCluster (string) - Optional Istio mesh cluster name from kiali_list_mesh_clusters (e.g. west). When omitted, Kiali defaults to its home cluster.namespace (string) - Namespace containing the Istio object. For 'list', if not provided, returns objects across all namespaces. For 'get', required.object (string) - Name of the Istio object. Required for 'get' action.serviceName (string) - Filter Istio configurations (VirtualServices, DestinationRules, and their referenced Gateways) that affect a specific service. Only applicable for 'list' actionversion (string) - API version. Use 'v1' for all resource types. Required for 'get' action.
-
kiali_manage_istio_config - Create, patch, or delete Istio, Gateway API, and Inference API config. Supports Istio resources (networking.istio.io, security.istio.io), Gateway API resources (gateway.networking.k8s.io), and Inference API resources (inference.networking.k8s.io) when installed on the cluster. For list and get (read-only) use manage_istio_config_read.
action (string) (required) - Action to perform (write)data (string) - JSON or YAML data for the resource. Required for create and patch actions. For create, you can provide partial content (e.g. only spec) and it will be merged onto a valid template with defaults. Arrays (like servers, http, etc.) are REPLACED entirely, so include ALL elements you want.group (string) (required) - API group of the Istio object. Use 'gateway.networking.k8s.io' for Gateway API resources. Use 'inference.networking.k8s.io' for Inference API resources.kind (string) (required) - Kind of the Istio object (e.g., 'VirtualService', 'DestinationRule').meshCluster (string) - Optional Istio mesh cluster name from kiali_list_mesh_clusters (e.g. west). When omitted, Kiali defaults to its home cluster.namespace (string) (required) - Namespace containing the Istio object.object (string) (required) - Name of the Istio object.version (string) (required) - API version. Use 'v1' for all resource types.
-
kiali_list_mesh_clusters - Returns the list of Istio mesh clusters that Kiali can access. Each entry includes its name and whether it is the home cluster (where Kiali is deployed). Call this tool before using meshCluster on other Kiali tools when the target cluster is unknown.
-
kiali_get_resource_details - Fetches a list of resources OR retrieves detailed data for a specific resource. If 'resourceName' is omitted, it returns a list. If 'resourceName' is provided, it returns details for that specific resource.
meshCluster (string) - Optional Istio mesh cluster name from kiali_list_mesh_clusters (e.g. west). When omitted, Kiali defaults to its home cluster.namespaces (string) - Comma-separated list of namespaces to query (e.g., 'bookinfo' or 'bookinfo,default'). If not provided, it will query across all accessible namespaces.resourceName (string) - Optional. The specific name of the resource. If left empty, the tool returns a list of all resources of the specified type. If provided, the tool returns deep details for this specific resource.resourceType (string) (required) - The type of resource to query. Use 'app' for Kiali applications (grouped by the Kubernetes 'app' label). Use 'argoapp' for ArgoCD Application CRDs (requires ArgoCD installed and the Kiali service account must have read permissions on applications.argoproj.io).
-
kiali_list_traces - Lists distributed traces for a service in a namespace. Returns a summary (namespace, service, total_found, avg_duration_ms) and a list of traces with id, duration_ms, spans_count, root_op, slowest_service, has_errors. Use get_trace_details with a trace id to get full hierarchy.
errorOnly (boolean) - If true, only consider traces that contain errors. Default false.limit (integer) - Maximum number of traces to return. Default 10.lookbackSeconds (integer) - How far back to search. Default 600 (10m).meshCluster (string) - Optional Istio mesh cluster name from kiali_list_mesh_clusters (e.g. west). When omitted, Kiali defaults to its home cluster.namespace (string) (required) - Kubernetes namespace of the service.serviceName (string) (required) - Service name to search traces for (required). Returns multiple traces up to limit.
-
kiali_get_trace_details - Fetches a single distributed trace by trace_id and returns its call hierarchy (service tree with duration, status, and nested calls). Use this after list_traces to drill into a specific trace.
traceId (string) (required) - Trace ID to fetch and summarize. If provided, namespace/service_name are ignored.
-
kiali_get_pod_performance - Returns a human-readable text summary with current Pod CPU/memory usage (from Prometheus) compared to Kubernetes requests/limits (from the Pod spec). Useful to answer questions like 'Is this workload using too much memory?'
meshCluster (string) - Optional Istio mesh cluster name from kiali_list_mesh_clusters (e.g. west). When omitted, Kiali defaults to its home cluster.namespace (string) (required) - Kubernetes namespace of the Pod.podName (string) - Kubernetes Pod name. If workloadName is provided, the tool will attempt to resolve a Pod from that workload first.queryTime (string) - Optional end timestamp (RFC3339) for the query. Defaults to now.timeRange (string) - Time window used to compute CPU rate (Prometheus duration like '5m', '10m', '1h', '1d'). Defaults to '10m'.workloadName (string) - Kubernetes Workload name (e.g. Deployment/StatefulSet/etc). Tool will look up the workload and pick one of its Pods. If not found, it will fall back to treating this value as a podName.
-
kiali_get_logs - Get the logs of a Kubernetes Pod (or workload name that will be resolved to a pod) in a namespace. Output is plain text, matching kubernetes-mcp-server pods_log. The line_count field tells you the total number of log lines returned. Analyze ALL of them, but summarize the results unless the user explicitly asks for the raw output. Do not omit any error or warning lines.
container (string) - Optional. Name of the Pod container to get the logs from.format (string) - Output formatting for chat. 'codeblock' wraps logs in ~~~ fences (recommended). 'plain' returns raw text like kubernetes-mcp-server pods_log.meshCluster (string) - Optional Istio mesh cluster name from kiali_list_mesh_clusters (e.g. west). When omitted, Kiali defaults to its home cluster.name (string) (required) - Name of the Pod to get the logs from. If it does not exist, it will be treated as a workload name and a running pod will be selected.namespace (string) (required) - Namespace to get the Pod logs fromprevious (boolean) - Optional. Return previous terminated container logsseverity (string) - Optional severity filter applied client-side. Accepts 'ERROR', 'WARN' or combinations like 'ERROR,WARN'.tail (integer) - Number of lines to retrieve from the end of the logs (Optional, defaults to 50). Cannot exceed 200 lines.workload (string) - Optional. Workload name override (used when name lookup fails).
-
kiali_get_metrics - Returns a compact JSON summary of Istio metrics (latency quantiles, traffic trends, throughput, payload sizes) for the given resource.
byLabels (string) - Comma-separated list of labels to group metrics by (e.g., 'source_workload,destination_service'). Optionaldirection (string) - Traffic direction. Optional, defaults to 'outbound'meshCluster (string) - Optional Istio mesh cluster name from kiali_list_mesh_clusters (e.g. west). When omitted, Kiali defaults to its home cluster.namespace (string) (required) - Namespace to get metrics fromquantiles (string) - Comma-separated list of quantiles for histogram metrics (e.g., '0.5,0.95,0.99'). OptionalrateInterval (string) - Rate interval for metrics (e.g., '1m', '5m'). Optional, defaults to '10m'reporter (string) - Metrics reporter(s). Comma-separated list of: 'source', 'destination', 'waypoint', or the special value 'both' (no reporter filter). Optional, defaults to 'source'. Example: 'source,waypoint'requestProtocol (string) - Filter by request protocol (e.g., 'http', 'grpc', 'tcp'). OptionalresourceName (string) (required) - Name of the resource to get metrics forresourceType (string) (required) - Type of resource to get metricsstep (string) - Step between data points in seconds (e.g., '15'). Optional, defaults to 15 seconds
-
vm_clone - Clone a VirtualMachine on KubeVirt by creating a VirtualMachineClone resource. This creates a copy of the source VM with a new name using the KubeVirt Clone API
name (string) (required) - The name of the source virtual machine to clonenamespace (string) (required) - The namespace of the source virtual machinetargetName (string) (required) - The name for the new cloned virtual machine
-
vm_console_screenshot - Capture a screenshot of the graphical (VNC) console of a VirtualMachine on KubeVirt as a PNG image. Use this to see what is currently displayed on the VM's screen (for example firmware, a bootloader, or a login prompt). Read-only: it never sends input to the guest.
name (string) (required) - The name of the virtual machinenamespace (string) (required) - The namespace of the virtual machine
-
vm_create - Create a VirtualMachine on KubeVirt with the specified configuration, automatically resolving instance types, preferences, and container disk images. VM will be created in Halted state by default; use autostart parameter to start it immediately.
autostart (boolean) - Optional flag to automatically start the VM after creation (sets runStrategy to Always instead of Halted). Defaults to false.instancetype (string) - Optional instance type name for the VM (e.g., 'u1.small', 'u1.medium', 'u1.large')name (string) (required) - The name of the virtual machinenamespace (string) (required) - The namespace for the virtual machinenetworks (array) - Optional secondary network interfaces to attach to the VM. Each item specifies a Multus NetworkAttachmentDefinition to attach. Accepts either simple strings (NetworkAttachmentDefinition names) or objects with 'name' (interface name in VM) and 'networkName' (NetworkAttachmentDefinition name) properties. Each network creates a bridge interface on the VM.performance (string) - Optional performance family hint for the VM instance type (e.g., 'u1' for general-purpose, 'o1' for overcommitted, 'c1' for compute-optimized, 'm1' for memory-optimized). Defaults to 'u1' (general-purpose) if not specified.preference (string) - Optional preference name for the VMsize (string) - Optional workload size hint for the VM (e.g., 'small', 'medium', 'large', 'xlarge'). Used to auto-select an appropriate instance type if not explicitly specified.storage (string) - Optional storage size for the VM's root disk when using DataSources (e.g., '30Gi', '50Gi', '100Gi'). Defaults to 30Gi. Ignored when using container disks.workload (string) - The workload for the VM. Accepts OS names (e.g., 'fedora' (default), 'ubuntu', 'centos', 'centos-stream', 'debian', 'rhel', 'opensuse', 'opensuse-tumbleweed', 'opensuse-leap') or full container disk image URLs
-
vm_guest_info - Get guest operating system information from a VirtualMachine's QEMU guest agent. Requires the guest agent to be installed and running inside the VM. Provides detailed information about the OS, filesystems, network interfaces, and logged-in users.
info_type (string) - Type of information to retrieve: 'all' (default - all available info), 'os' (operating system details), 'filesystem' (disk and filesystem info), 'users' (logged-in users), 'network' (network interfaces and IPs)name (string) (required) - The name of the virtual machinenamespace (string) (required) - The namespace of the virtual machine
-
vm_lifecycle - Manage KubeVirt VirtualMachine lifecycle: start, stop, restart, pause, or unpause a VM
action (string) (required) - The lifecycle action to perform: 'start' (changes runStrategy to Always), 'stop' (changes runStrategy to Halted), 'restart' (stops then starts the VM), 'pause' (suspends the running VMI in-place), or 'unpause' (resumes a paused VMI)name (string) (required) - The name of the virtual machinenamespace (string) (required) - The namespace of the virtual machine
-
vm_create_from_template - Create a VirtualMachine from a VirtualMachineTemplate (virt-template) on KubeVirt. Processes the template server-side to substitute parameters (required values, defaults, and auto-generated values like passwords), then creates the resulting VirtualMachine in the same namespace. Cross-namespace template usage is not supported.
namespace (string) (required) - The namespace of the VirtualMachineTemplate and the resulting VirtualMachine (must be the same)parameters (object) - Parameter values to substitute in the template. Keys are parameter names (e.g. VM_NAME), values are strings. Required parameters must be provided; optional parameters use their defaults if omitted; parameters with generate/from will be auto-generated if not provided.template_name (string) (required) - The name of the VirtualMachineTemplate to create the VM from
-
vm_troubleshoot - Diagnose KubeVirt VirtualMachine issues with automated root-cause detection. Collects VM status, VMI status, volumes, DataVolume/PVC state, cloud-init configuration, pod state, logs, and events, then runs heuristic checks to identify specific problems and suggest fixes. Returns a 'Detected Issues' section with CRITICAL/WARNING findings and actionable remediation steps, followed by raw diagnostic data. Use this tool FIRST whenever a user asks why a VM is not starting, stuck in Provisioning, crashlooping, failing to migrate, or exhibiting unexpected behavior. Automatically detects: missing StorageClasses, invalid PVC specs, dangerous cloud-init commands (shutdown/halt), nodeSelector migration blockers, failed migrations, and pod crashloops. If the user asks to fix or remediate the issue, use the Suggested Fixes from the report with vm_lifecycle (restart) or resources_create_or_update.
name (string) (required) - The name of the VirtualMachine to troubleshootnamespace (string) (required) - The namespace of the VirtualMachine to troubleshoot
- netobserv_list_flows - Lists NetObserv network flow records from Loki. Use when investigating traffic between workloads, IPs, ports, or protocols in a namespace or time window.
endTime (integer) - End of time range as Unix epoch seconds. Defaults to now.filters (string) - NetObserv filter expression passed to the console plugin (plain text; the client URL-encodes it).
Syntax:
- key=value — exact match; key=a,b — OR multiple values for the same key
- key~pattern — regex / contains match; key!~pattern — NOT regex
- key!=value — not equal; key>number — numeric greater-or-equal (e.g. Bytes>1000)
- AND within a group: & (e.g. SrcK8S_Namespace=default&Proto=6)
- OR between groups: | (e.g. SrcK8S_Name=pod-a|SrcK8S_Name=pod-b)
Prefer the dedicated "namespace" parameter for namespace scope when possible.
Use Kubernetes list tools (namespaces, pods, deployments, etc.) to discover filter values.
Common Kubernetes fields (Src/Dst prefixes mirror each other):
- SrcK8S_Namespace, DstK8S_Namespace, SrcK8S_Name, DstK8S_Name
- SrcK8S_Type, DstK8S_Type (e.g. Pod, Service, Node)
- SrcK8S_OwnerName, DstK8S_OwnerName, SrcK8S_OwnerType, DstK8S_OwnerType (for Deployment, StatefulSet, etc.)
- SrcK8S_HostName, DstK8S_HostName, SrcK8S_Zone, DstK8S_Zone, K8S_ClusterName, UDN
Network & flow:
- SrcAddr, DstAddr (IPs), SrcPort, DstPort, Proto (IANA number, e.g. 6=TCP, 17=UDP)
- FlowDirection (0=Ingress, 1=Egress, 2=Inner), Bytes, Packets, Dscp, Flags
Packet drops (often with recordType flowLog and packetLoss dropped/hasDrops):
- PktDropPackets, PktDropBytes, PktDropLatestState, PktDropLatestDropCause
DNS:
- DnsName, DnsId, DnsLatencyMs, DnsErrno, DnsFlagsResponseCode
Examples:
-
SrcK8S_Namespace=openshift-netobserv&SrcK8S_Name~my-app
-
Proto=6&DstPort=443
-
SrcK8S_Name=pod-a|SrcK8S_Name=pod-b
limit (integer) - Maximum number of flow records to return. Default 100.namespace (string) - Restrict results to flows where source or destination namespace matches (dev-scoped Loki tenant).packetLoss (string) - Packet loss filter.recordType (string) - Flow record type filter.startTime (integer) - Start of time range as Unix epoch seconds. Overrides timeRange when set.timeRange (integer) - Lookback window in seconds when startTime is omitted. Default 300.
-
netobserv_export_flows - Exports NetObserv flow records as CSV with the same filters as list_flows. Use when the user needs downloadable flow data for audits or offline analysis.
columns (string) - Optional comma-separated column names to include (e.g. SrcK8S_Namespace,DstK8S_Namespace,Bytes). Omit to export all columns present in the result.endTime (integer) - End of time range as Unix epoch seconds. Defaults to now.filters (string) - NetObserv filter expression passed to the console plugin (plain text; the client URL-encodes it).
Syntax:
- key=value — exact match; key=a,b — OR multiple values for the same key
- key~pattern — regex / contains match; key!~pattern — NOT regex
- key!=value — not equal; key>number — numeric greater-or-equal (e.g. Bytes>1000)
- AND within a group: & (e.g. SrcK8S_Namespace=default&Proto=6)
- OR between groups: | (e.g. SrcK8S_Name=pod-a|SrcK8S_Name=pod-b)
Prefer the dedicated "namespace" parameter for namespace scope when possible.
Use Kubernetes list tools (namespaces, pods, deployments, etc.) to discover filter values.
Common Kubernetes fields (Src/Dst prefixes mirror each other):
- SrcK8S_Namespace, DstK8S_Namespace, SrcK8S_Name, DstK8S_Name
- SrcK8S_Type, DstK8S_Type (e.g. Pod, Service, Node)
- SrcK8S_OwnerName, DstK8S_OwnerName, SrcK8S_OwnerType, DstK8S_OwnerType (for Deployment, StatefulSet, etc.)
- SrcK8S_HostName, DstK8S_HostName, SrcK8S_Zone, DstK8S_Zone, K8S_ClusterName, UDN
Network & flow:
- SrcAddr, DstAddr (IPs), SrcPort, DstPort, Proto (IANA number, e.g. 6=TCP, 17=UDP)
- FlowDirection (0=Ingress, 1=Egress, 2=Inner), Bytes, Packets, Dscp, Flags
Packet drops (often with recordType flowLog and packetLoss dropped/hasDrops):
- PktDropPackets, PktDropBytes, PktDropLatestState, PktDropLatestDropCause
DNS:
- DnsName, DnsId, DnsLatencyMs, DnsErrno, DnsFlagsResponseCode
Examples:
-
SrcK8S_Namespace=openshift-netobserv&SrcK8S_Name~my-app
-
Proto=6&DstPort=443
-
SrcK8S_Name=pod-a|SrcK8S_Name=pod-b
format (string) - Export format. Only csv is supported.limit (integer) - Maximum number of flow records to return. Default 100.namespace (string) - Restrict results to flows where source or destination namespace matches (dev-scoped Loki tenant).packetLoss (string) - Packet loss filter.recordType (string) - Flow record type filter.startTime (integer) - Start of time range as Unix epoch seconds. Overrides timeRange when set.timeRange (integer) - Lookback window in seconds when startTime is omitted. Default 300.
-
netobserv_get_flow_metrics - Returns aggregated NetObserv flow metrics as topology or time-series data. Use for throughput, TLS/DNS/drop breakdowns, and namespace or workload traffic analysis; see aggregateBy and groups for grouping options.
aggregateBy (string) (required) - Primary dimension for netobserv_get_flow_metrics (console plugin /api/flow/metrics).
Two forms (use exact spelling):
- Topology scopes — aggregate endpoints for graph/topology views:
- app — application workloads (pods/services), excluding infrastructure traffic
- namespace — Kubernetes namespace (default)
- owner — controller owner (Deployment, StatefulSet, …)
- resource — pod, service, or node (finest workload granularity)
- host — node name
- zone — availability zone
- cluster — cluster name (multi-cluster)
- network — user-defined / secondary network name
- Flow record fields — group by a single flow attribute (PascalCase field name).
Use for breakdown charts (TLS, DNS, drops, protocol). Field names match filters / flow logs.
TLS (requires TLS tracking on the FlowCollector):
- TLSVersion, TLSCipherSuite, TLSGroup, TLSTypes
DNS:
- DnsName, DnsFlagsResponseCode, DnsErrno
Packet drops:
- PktDropLatestState, PktDropLatestDropCause
Network / K8s (single-sided breakdown; pair with filters for src/dst):
- Proto, SrcPort, DstPort, FlowDirection, Dscp
- SrcK8S_Namespace, DstK8S_Namespace, SrcK8S_Name, DstK8S_Name
- SrcK8S_Type, DstK8S_Type, SrcK8S_OwnerName, DstK8S_OwnerName
- SrcK8S_HostName, DstK8S_HostName, SrcK8S_Zone, DstK8S_Zone
- K8S_ClusterName, SrcK8S_NetworkName, DstK8S_NetworkName
Pair aggregateBy with type and function:
- Throughput: type=Bytes or Packets, function=rate
- Flow count: type=Flows, function=count or rate
- DNS volume: type=DnsFlows, function=count
- DNS latency: type=DnsLatencyMs, function=avg, p90, or max
- RTT: type=TimeFlowRttNs, function=avg, min, or p90
- Drops: type=PktDropPackets or PktDropBytes, function=rate
Examples:
- aggregateBy=namespace, type=Bytes, function=rate
- aggregateBy=TLSVersion, type=Bytes, function=rate, filters=TLSTypes!~""
- aggregateBy=TLSGroup, type=Flows, function=count
- aggregateBy=DnsFlagsResponseCode, type=DnsFlows, function=count
- aggregateBy=PktDropLatestState, type=PktDropPackets, function=rate, packetLoss=dropped
- aggregateBy=resource, type=Bytes, function=rate, namespace=netobserv
dataSource (string) - Metrics backend: auto (prefer Prometheus, fallback to Loki), prom, or loki.endTime (integer) - End of time range as Unix epoch seconds. Defaults to now.filters (string) - NetObserv filter expression passed to the console plugin (plain text; the client URL-encodes it).
Syntax:
- key=value — exact match; key=a,b — OR multiple values for the same key
- key~pattern — regex / contains match; key!~pattern — NOT regex
- key!=value — not equal; key>number — numeric greater-or-equal (e.g. Bytes>1000)
- AND within a group: & (e.g. SrcK8S_Namespace=default&Proto=6)
- OR between groups: | (e.g. SrcK8S_Name=pod-a|SrcK8S_Name=pod-b)
Prefer the dedicated "namespace" parameter for namespace scope when possible.
Use Kubernetes list tools (namespaces, pods, deployments, etc.) to discover filter values.
Common Kubernetes fields (Src/Dst prefixes mirror each other):
- SrcK8S_Namespace, DstK8S_Namespace, SrcK8S_Name, DstK8S_Name
- SrcK8S_Type, DstK8S_Type (e.g. Pod, Service, Node)
- SrcK8S_OwnerName, DstK8S_OwnerName, SrcK8S_OwnerType, DstK8S_OwnerType (for Deployment, StatefulSet, etc.)
- SrcK8S_HostName, DstK8S_HostName, SrcK8S_Zone, DstK8S_Zone, K8S_ClusterName, UDN
Network & flow:
- SrcAddr, DstAddr (IPs), SrcPort, DstPort, Proto (IANA number, e.g. 6=TCP, 17=UDP)
- FlowDirection (0=Ingress, 1=Egress, 2=Inner), Bytes, Packets, Dscp, Flags
Packet drops (often with recordType flowLog and packetLoss dropped/hasDrops):
- PktDropPackets, PktDropBytes, PktDropLatestState, PktDropLatestDropCause
DNS:
- DnsName, DnsId, DnsLatencyMs, DnsErrno, DnsFlagsResponseCode
Examples:
- SrcK8S_Namespace=openshift-netobserv&SrcK8S_Name~my-app
- Proto=6&DstPort=443
- SrcK8S_Name=pod-a|SrcK8S_Name=pod-b
function (string) - Aggregation function.groups (string) - Optional comma-separated parent scopes when aggregateBy is a topology scope.
Adds extra label dimensions (e.g. break namespace results down by cluster or zone).
Ignored or less useful when aggregateBy is already a raw flow field (e.g. TLSVersion); use filters instead.
Single scopes:
- clusters, networks, zones, hosts, namespaces, owners
Combined scopes (use +, no spaces):
- clusters+zones, clusters+hosts, clusters+namespaces, clusters+owners
- zones+hosts, zones+namespaces, zones+owners
- hosts+namespaces, hosts+owners
- namespaces+owners
- networks+zones, networks+hosts, networks+namespaces, networks+owners
Examples:
- aggregateBy=namespace, groups=clusters
- aggregateBy=resource, groups=namespaces
- aggregateBy=owner, groups=zones,hosts
limit (integer) - Maximum number of flow records to return. Default 100.namespace (string) - Restrict results to flows where source or destination namespace matches (dev-scoped Loki tenant).packetLoss (string) - Packet loss filter.rateInterval (string) - Prometheus rate interval (e.g. 1m, 5m).recordType (string) - Flow record type filter.startTime (integer) - Start of time range as Unix epoch seconds. Overrides timeRange when set.step (string) - Query resolution step (e.g. 30s, 1m).timeRange (integer) - Lookback window in seconds when startTime is omitted. Default 300.type (string) - Metric type to aggregate.
-
loki_list_instances - List LokiStack instances available in the Kubernetes cluster.
Call this first when using Loki Operator managed stacks so you can pass lokiNamespace and lokiName to other Loki tools.
-
loki_label_names - List available Loki label names for a time range. Use this before writing LogQL queries.
end (string) - End time as RFC3339, Unix timestamp, NOW, or NOW-relative expression (optional).lokiName (string) - Name of the LokiStack. Use loki_list_instances to discover valid values.lokiNamespace (string) - Kubernetes namespace of the LokiStack. Use loki_list_instances to discover valid values.start (string) - Start time as RFC3339, Unix timestamp, NOW, or NOW-relative expression (optional).tenant (string) - Loki tenant ID (X-Scope-OrgID). For LokiStack gateway modes (e.g. openshift-network) this selects the /api/logs/v1/<tenant> path; use network for openshift-network.
-
loki_label_values - List possible values for a Loki label key. Use this to build precise label matchers in LogQL.
end (string) - End time as RFC3339, Unix timestamp, NOW, or NOW-relative expression (optional).label (string) (required) - Label key to inspect (for example namespace, pod, container).lokiName (string) - Name of the LokiStack. Use loki_list_instances to discover valid values.lokiNamespace (string) - Kubernetes namespace of the LokiStack. Use loki_list_instances to discover valid values.start (string) - Start time as RFC3339, Unix timestamp, NOW, or NOW-relative expression (optional).tenant (string) - Loki tenant ID (X-Scope-OrgID). For LokiStack gateway modes (e.g. openshift-network) this selects the /api/logs/v1/<tenant> path; use network for openshift-network.
-
loki_query_range - Execute a Loki LogQL range query and return matching log streams and lines.
Use precise label matchers and a short time window first.
direction (string) - Search direction: backward (default) or forward.duration (string) - Lookback duration from now when start/end are omitted (for example 5m, 1h). Defaults to 15m.end (string) - End time as RFC3339, Unix timestamp, NOW, or NOW-relative expression (optional).limit (integer) - Maximum number of log lines to return. Defaults to 100, max 1000.lokiName (string) - Name of the LokiStack. Use loki_list_instances to discover valid values.lokiNamespace (string) - Kubernetes namespace of the LokiStack. Use loki_list_instances to discover valid values.query (string) (required) - LogQL query string.start (string) - Start time as RFC3339, Unix timestamp, NOW, or NOW-relative expression (optional).tenant (string) - Loki tenant ID (X-Scope-OrgID). For LokiStack gateway modes (e.g. openshift-network) this selects the /api/logs/v1/<tenant> path; use network for openshift-network.
- list_metrics - MANDATORY FIRST STEP: List all available metric names in Prometheus.
YOU MUST CALL THIS TOOL BEFORE ANY OTHER QUERY TOOL
This tool MUST be called first for EVERY observability question to:
- Discover what metrics actually exist in this environment
- Find the EXACT metric name to use in queries
- Avoid querying non-existent metrics
- The 'name_regex' parameter should always be provided, and be a best guess of what the metric would be named like.
- Do not use a blanket regex like .* or .+ in the 'name_regex' parameter. Use specific ones like kube., node., etc.
REGEX PATTERN GUIDANCE:
- Prometheus metrics are typically prefixed (e.g., 'prometheus_tsdb_head_series', 'kube_pod_status_phase')
- To match metrics CONTAINING a substring, use wildcards: '.tsdb.' matches 'prometheus_tsdb_head_series'
- Without wildcards, the pattern matches EXACTLY: 'tsdb' only matches a metric literally named 'tsdb' (which rarely exists)
- Common patterns: 'kube_pod.' (pods), '.memory.' (memory-related), 'node_.' (node metrics)
- If you get empty results, try adding '.*' before/after your search term
NEVER skip this step. NEVER guess metric names. Metric names vary between environments.
After calling this tool:
- Search the returned list for relevant metrics
- Use the EXACT metric name found in subsequent queries
- If no relevant metric exists, inform the user
-
name_regex (string) (required) - Regex pattern to filter metric names. IMPORTANT: Metric names are typically prefixed (e.g., 'prometheus_tsdb_head_series'). Use wildcards to match substrings: '.tsdb.' matches any metric containing 'tsdb', while 'tsdb' only matches the exact string 'tsdb'. Examples: 'http_.' (starts with http_), '.memory.' (contains memory), 'node_.' (starts with node_). This parameter is required. Don't pass in blanket regex like '.*' or '.+'.
-
execute_instant_query - Execute a PromQL instant query to get current/point-in-time values.
PREREQUISITE: You MUST call list_metrics first to verify the metric exists
WHEN TO USE:
- Current state questions: "What is the current error rate?"
- Point-in-time snapshots: "How many pods are running?"
- Latest values: "Which pods are in Pending state?"
The 'query' parameter MUST use metric names that were returned by list_metrics.
-
query (string) (required) - PromQL query string using metric names verified via list_metrics
-
time (string) - Evaluation time as RFC3339 or Unix timestamp. Omit or use 'NOW' for current time.
-
execute_range_query - Execute a PromQL range query to get time-series data over a period.
PREREQUISITE: You MUST call list_metrics first to verify the metric exists
WHEN TO USE:
- Trends over time: "What was CPU usage over the last hour?"
- Rate calculations: "How many requests per second?"
- Historical analysis: "Were there any restarts in the last 5 minutes?"
TIME PARAMETERS:
- 'duration': Look back from now (e.g., "5m", "1h", "24h")
- 'step': Data point resolution (e.g., "1m" for 1-hour duration, "5m" for 24-hour duration)
The 'query' parameter MUST use metric names that were returned by list_metrics.
-
duration (string) - Duration to look back from now (e.g., '1h', '30m', '1d', '2w') (optional)
-
end (string) - End time as RFC3339 or Unix timestamp (optional). Use NOW for current time.
-
query (string) (required) - PromQL query string using metric names verified via list_metrics
-
start (string) - Start time as RFC3339 or Unix timestamp (optional)
-
step (string) (required) - Query resolution step width (e.g., '15s', '1m', '1h'). Choose based on time range: shorter ranges use smaller steps.
-
show_timeseries - Display the results as an interactive timeseries chart.
This tool works like execute_range_query but renders the results as a visual chart in the UI clients.
Use it when the user wants to see a graph or visualization of time-series data and to use visuals to provide the answer.
Use the show_timeseries as the last tool call after all the other Prometheus tool calls where finalized.
TIME PARAMETERS:
- 'duration': Look back from now (e.g., "5m", "1h", "24h")
- 'step': Data point resolution (e.g., "1m" for 1-hour duration, "5m" for 24-hour duration)
- 'title': A descriptive chart title (e.g., "API Error Rate Over Last Hour")
- 'description': An explanation of the chart's meaning or context (e.g., "Shows the rate of HTTP 5xx errors per second, broken down by pod")
The 'query' parameter MUST be a range query and must use metric names that were returned by list_metrics.
-
description (string) - Explanation of the chart's meaning or context (e.g., 'Shows the rate of HTTP 5xx errors per second, broken down by pod'). Displayed below the title when provided.
-
duration (string) - Duration to look back from now (e.g., '1h', '30m', '1d', '2w') (optional)
-
end (string) - End time as RFC3339 or Unix timestamp (optional). Use NOW for current time.
-
query (string) (required) - PromQL query string using metric names verified via list_metrics
-
start (string) - Start time as RFC3339 or Unix timestamp (optional)
-
step (string) (required) - Query resolution step width (e.g., '15s', '1m', '1h'). Choose based on time range: shorter ranges use smaller steps.
-
title (string) - Human-readable chart title describing what the query shows (e.g., 'API Error Rate Over Last Hour'). Displayed above the chart when provided.
-
get_label_names - Get all label names (dimensions) available for filtering a metric.
WHEN TO USE (after calling list_metrics):
- To discover how to filter metrics (by namespace, pod, service, etc.)
- Before constructing label matchers in PromQL queries
The 'metric' parameter should use a metric name from list_metrics output.
-
end (string) - End time for label discovery as RFC3339 or Unix timestamp (optional, defaults to now)
-
metric (string) - Metric name (from list_metrics) to get label names for. Leave empty for all metrics.
-
start (string) - Start time for label discovery as RFC3339 or Unix timestamp (optional, defaults to 1 hour ago)
-
get_label_values - Get all unique values for a specific label.
WHEN TO USE (after calling list_metrics and get_label_names):
- To find exact label values for filtering (namespace names, pod names, etc.)
- To see what values exist before constructing queries
The 'metric' parameter should use a metric name from list_metrics output.
-
end (string) - End time for label value discovery as RFC3339 or Unix timestamp (optional, defaults to now)
-
label (string) (required) - Label name (from get_label_names) to get values for
-
metric (string) - Metric name (from list_metrics) to scope the label values to. Leave empty for all metrics.
-
start (string) - Start time for label value discovery as RFC3339 or Unix timestamp (optional, defaults to 1 hour ago)
-
get_series - Get time series matching selectors and preview cardinality.
WHEN TO USE (optional, after calling list_metrics):
- To verify label filters match expected series before querying
- To check cardinality and avoid slow queries
CARDINALITY GUIDANCE:
- <100 series: Safe
- 100-1000: Usually fine
-
1000: Add more label filters
The selector should use metric names from list_metrics output.
-
end (string) - End time for series discovery as RFC3339 or Unix timestamp (optional, defaults to now)
-
matches (string) (required) - PromQL series selector using metric names from list_metrics
-
start (string) - Start time for series discovery as RFC3339 or Unix timestamp (optional, defaults to 1 hour ago)
-
get_alerts - Get alerts from Alertmanager.
WHEN TO USE:
- START HERE when investigating issues: if the user asks about things breaking, errors, failures, outages, services being down, or anything going wrong in the cluster
- When the user mentions a specific alert name - use this tool to get the alert's full labels (namespace, pod, service, etc.) which are essential for further investigation with other tools
- To see currently firing alerts in the cluster
- To check which alerts are active, silenced, or inhibited
- To understand what's happening before diving into metrics or logs
INVESTIGATION TIP: Alert labels often contain the exact identifiers (pod names, namespaces, job names) needed for targeted queries with prometheus tools.
FILTERING:
- Use 'active' to filter for only active alerts (not resolved)
- Use 'silenced' to filter for silenced alerts
- Use 'inhibited' to filter for inhibited alerts
- Use 'filter' to apply label matchers (e.g., "alertname=HighCPU")
- Use 'receiver' to filter alerts by receiver name
All filter parameters are optional. Without filters, all alerts are returned.
-
active (boolean) - Filter for active alerts only (true/false, optional)
-
filter (string) - Label matchers to filter alerts (e.g., 'alertname=HighCPU', optional)
-
inhibited (boolean) - Filter for inhibited alerts only (true/false, optional)
-
receiver (string) - Receiver name to filter alerts (optional)
-
silenced (boolean) - Filter for silenced alerts only (true/false, optional)
-
unprocessed (boolean) - Filter for unprocessed alerts only (true/false, optional)
-
get_silences - Get silences from Alertmanager.
WHEN TO USE:
- To see which alerts are currently silenced
- To check active, pending, or expired silences
- To investigate why certain alerts are not firing notifications
FILTERING:
- Use 'filter' to apply label matchers to find specific silences
Silences are used to temporarily mute alerts based on label matchers. This tool helps you understand what is currently silenced in your environment.
filter (string) - Label matchers to filter silences (e.g., 'alertname=HighCPU', optional)
-
otelcol_list_components - List available OpenTelemetry Collector components (receivers, processors, exporters, extensions, connectors) for a given version.
version (string) - Collector version (e.g., 'v0.100.0'). Defaults to latest available.
-
otelcol_get_component_schema - Get the JSON schema for an OpenTelemetry Collector component's configuration options.
component_name (string) (required) - Component name from otelcol_list_components (e.g., 'otlp', 'batch', 'debug')component_type (string) (required) - Component type: receiver, processor, exporter, extension, connectorversion (string) - Collector version (e.g., 'v0.100.0'). Defaults to latest available.
-
otelcol_validate_config - Validate an OpenTelemetry Collector component configuration against its JSON schema.
component_name (string) (required) - Component name from otelcol_list_components (e.g., 'otlp', 'batch', 'debug')component_type (string) (required) - Component type: receiver, processor, exporter, extension, connectorconfig (string) (required) - Configuration to validate as YAML or JSON stringformat (string) - Config format: 'yaml' (default) or 'json'version (string) - Collector version (e.g., 'v0.100.0'). Defaults to latest available.
-
otelcol_get_versions - List available OpenTelemetry Collector versions and identify the latest.
-
tempo_list_instances - List all Tempo instances available in the Kubernetes cluster.
Call this tool first to discover available Tempo instances before using other Tempo tools,
as the returned namespace, name, and tenant values are required parameters for all other Tempo tools.
Always print the output of this tool in a table.
-
tempo_get_trace_by_id - Retrieve a single distributed trace by its trace ID from Tempo.
Returns the full trace with all its spans, including service names, operation names, durations, and attributes.
Use this tool when you already have a specific trace ID, e.g. from search results or logs.
end (string) - Optional end of the time range in RFC 3339 format, e.g. "2025-01-02T00:00:00Z".
Narrows the time range to improve query performance.start (string) - Optional start of the time range in RFC 3339 format, e.g. "2025-01-01T00:00:00Z".
Narrows the time range to improve query performance.tempoName (string) (required) - The name of the Tempo instance to query. Use tempo_list_instances to discover available instance names.tempoNamespace (string) (required) - The Kubernetes namespace where the Tempo instance is deployed. Use tempo_list_instances to discover available namespaces.tenant (string) - The tenant to query. This parameter is required for multi-tenant instances. Use tempo_list_instances to discover available tenants for each instance.traceid (string) (required) - The trace ID to retrieve, e.g. "26dad4a0e2b0dd9a440dd5ff203a24a4".
-
tempo_search_traces - Search for distributed traces in Tempo using TraceQL.
Use this tool to find traces matching specific criteria such as service name, HTTP status code, duration, or other span or resource attributes.
IMPORTANT — "slow" or "long" trace requests: Do NOT guess a duration threshold.
First call this tool WITHOUT a duration filter to establish a latency baseline, then use that baseline to set a sensible threshold.
Both steps are required — do NOT skip the second search with the duration filter.
Skip this two-step process only when the user provides an explicit duration (e.g. "find traces slower than 2s").
end (string) - End of the time range in RFC 3339 format, e.g. "2025-01-01T00:00:00Z".
Use "NOW" for current time.
Both start and end should be provided to search the full time range; if omitted, only a small window of recent data is searched.limit (integer) - Maximum number of traces to return. Defaults to the server-side limit if not specified.query (string) (required) - A TraceQL query expression. Format:
query: "{ <filters joined by &&> }"
Filters:
- service name: resource.service.name="" (string, use quotes)
- HTTP status code: span.http.response.status_code= (number, no quotes)
- duration: duration><value like 100ms, 2s, 5m> (no quotes)
- error status: status=error (keyword, NO quotes — do NOT write status="error")
IMPORTANT: status values (error, ok, unset) are keywords, NOT strings. Write status=error, NEVER status="error".
Operators: =, !=, >, <, >=, <=
Common attributes:
- resource.service.name (service name)
- resource.k8s.namespace.name (Kubernetes namespace)
- resource.k8s.deployment.name (Kubernetes deployment)
- resource.k8s.statefulset.name (Kubernetes statefulset)
- resource.k8s.daemonset.name (Kubernetes daemonset)
- resource.k8s.replicaset.name (Kubernetes replicaset)
- resource.k8s.pod.name (Kubernetes pod)
- resource.k8s.container.name (Kubernetes container)
- resource.k8s.job.name (Kubernetes job)
- resource.k8s.cronjob.name (Kubernetes cronjob)
- resource.k8s.node.name (Kubernetes node)
- resource.k8s.cluster.name (Kubernetes cluster)
- span.http.response.status_code (HTTP response code)
- span.http.request.method (HTTP method like GET, POST)
- span.url.full (request URL)
- name (span name / operation name, e.g. "GET /api/users")
- duration (trace duration, e.g. 100ms, 2s)
- status (trace status: ok, error, unset)
Note: older instrumentation may use legacy HTTP attribute names (e.g. span.http.status_code instead of span.http.response.status_code).
If a query returns no results, try tempo_search_tags to check which attributes exist.
IMPORTANT:
- Always wrap filters in curly braces { }.
- Do NOT use SQL, PromQL, or Lucene syntax.
- Do NOT omit the "resource." or "span." prefix from attribute names
- When the user refers to a Kubernetes resource type (deployment, pod, namespace, etc.), use the matching resource.k8s.* attribute, NOT resource.service.name.
Examples:
- { resource.service.name="frontend" }
- { resource.k8s.deployment.name="checkout" && span.http.response.status_code>=500 }
- { status=error && duration>2s }
If unsure which attributes to filter on, use tempo_search_tags to discover available attributes before building a query.
-
spss (integer) - Maximum number of matching spans to return per trace.
-
start (string) - Start of the time range in RFC 3339 format, e.g. "2025-01-01T00:00:00Z".
Use "NOW" for current time.
Both start and end should be provided to search the full time range; if omitted, only a small window of recent data is searched.
-
tempoName (string) (required) - The name of the Tempo instance to query. Use tempo_list_instances to discover available instance names.
-
tempoNamespace (string) (required) - The Kubernetes namespace where the Tempo instance is deployed. Use tempo_list_instances to discover available namespaces.
-
tenant (string) - The tenant to query. This parameter is required for multi-tenant instances. Use tempo_list_instances to discover available tenants for each instance.
-
tempo_search_tags - List available tag names (attribute keys) in Tempo, grouped by scope.
Use this tool to discover which attributes are available for building TraceQL queries with tempo_search_traces.
For example, this tool may reveal tag names like "service.name" (in the "resource" scope) or "http.response.status_code" (in the "span" scope).
To use these in TraceQL queries, prefix them with their scope, e.g. "resource.service.name" or "span.http.response.status_code".
end (string) - Optional end of the time range (in RFC 3339 format, e.g. "2025-01-01T00:00:00Z") to filter which traces are considered when listing tags.limit (integer) - Maximum number of tag names to return per scope.maxStaleValues (integer) - Maximum number of consecutive blocks without new tag names before the search stops early. Higher values are more thorough but slower.query (string) - Optional TraceQL query to filter which traces are considered when listing tags,
e.g. '{ resource.service.name="payment-service" }' to only show tags present in traces from the 'payment-service' service.scope (string) - Filter tags to a specific scope. One of:
"resource" (service-level attributes like service.name),
"span" (individual span attributes like http.response.status_code),
"intrinsic" (built-in fields like duration, status, name).
If omitted, tags from all scopes are returned.start (string) - Optional start of the time range (in RFC 3339 format, e.g. "2025-01-01T00:00:00Z") to filter which traces are considered when listing tags.tempoName (string) (required) - The name of the Tempo instance to query. Use tempo_list_instances to discover available instance names.tempoNamespace (string) (required) - The Kubernetes namespace where the Tempo instance is deployed. Use tempo_list_instances to discover available namespaces.tenant (string) - The tenant to query. This parameter is required for multi-tenant instances. Use tempo_list_instances to discover available tenants for each instance.
-
tempo_search_tag_values - List the known values for a specific tag (attribute key) in Tempo.
Use this tool to discover what values exist for a given tag, e.g. to find all service names (values of "resource.service.name") or all HTTP methods (values of "span.http.request.method").
This is useful for building accurate TraceQL queries with tempo_search_traces.
end (string) - Optional end of the time range (in RFC 3339 format, e.g. "2025-01-01T00:00:00Z") to filter which traces are considered when listing values.limit (integer) - Maximum number of tag values to return.maxStaleValues (integer) - Maximum number of consecutive blocks without new values before the search stops early. Higher values are more thorough but slower.query (string) - Optional TraceQL query to filter which traces are considered when listing values,
e.g. '{ resource.service.name="payment-service" }' to only show tag values from the 'payment-service' service.start (string) - Optional start of the time range (in RFC 3339 format, e.g. "2025-01-01T00:00:00Z") to filter which traces are considered when listing values.tag (string) (required) - The fully qualified tag name to get values for, including its scope prefix, e.g. "resource.service.name" or "span.http.response.status_code".
Use tempo_search_tags to discover available tag names.tempoName (string) (required) - The name of the Tempo instance to query. Use tempo_list_instances to discover available instance names.tempoNamespace (string) (required) - The Kubernetes namespace where the Tempo instance is deployed. Use tempo_list_instances to discover available namespaces.tenant (string) - The tenant to query. This parameter is required for multi-tenant instances. Use tempo_list_instances to discover available tenants for each instance.
-
tekton_pipeline_start - Start a Tekton Pipeline by creating a PipelineRun that references it
name (string) (required) - Name of the Pipeline to startnamespace (string) - Namespace of the Pipelineparams (object) - Parameter values to pass to the Pipeline. Keys are parameter names; values can be a string, an array of strings, or an object (map of string to string) depending on the parameter type defined in the Pipeline spec
-
tekton_pipelinerun_lifecycle - Manage a Tekton PipelineRun lifecycle by restarting it with the same spec or cancelling it by setting spec.status to Cancelled.
action (string) (required) - Lifecycle action to perform: 'restart' creates a new PipelineRun with the same spec; 'cancel' sets spec.status to Cancelled.name (string) (required) - Name of the PipelineRun to managenamespace (string) - Namespace of the PipelineRun
-
tekton_pipelinerun_logs - Get logs for all TaskRuns owned by a Tekton PipelineRun. Use this to inspect PipelineRun execution output without locating pods manually.
name (string) (required) - Name of the PipelineRun to get logs fromnamespace (string) - Namespace of the PipelineRunstep (string) - Step name to include within matching TaskRunstail (integer) - Number of lines to retrieve from the end of each container log (default: 100)task (string) - Pipeline task name to filter by (tekton.dev/pipelineTask label)
-
tekton_task_start - Start a Tekton Task by creating a TaskRun that references it
name (string) (required) - Name of the Task to startnamespace (string) - Namespace of the Taskparams (object) - Parameter values to pass to the Task. Keys are parameter names; values can be a string, an array of strings, or an object (map of string to string) depending on the parameter type defined in the Task spec
-
tekton_taskrun_restart - Restart a Tekton TaskRun by creating a new TaskRun with the same spec
name (string) (required) - Name of the TaskRun to restartnamespace (string) - Namespace of the TaskRun
-
tekton_taskrun_logs - Get the logs from a Tekton TaskRun by resolving its underlying pod
name (string) (required) - Name of the TaskRun to get logs fromnamespace (string) - Namespace of the TaskRunstep (string) - Step name to include. If omitted, logs from all steps and sidecars are returnedtail (integer) - Number of lines to retrieve from the end of the logs (Optional, default: 100)
Prompts
- cluster-health-check - Perform comprehensive health assessment of Kubernetes/OpenShift cluster
namespace (string) - Optional namespace to limit health check scope (default: all namespaces)check_events (string) - Include recent warning/error events (true/false, default: true)
-
mesh-list-applications - List applications in the mesh namespaces
namespace (string) - Optional namespace to filter applications (default: all namespaces)
-
list-istio-config - List Istio configuration resources in the mesh namespaces
namespace (string) - Optional namespace to filter Istio configuration (default: all namespaces)
-
mesh-list-namespaces - List all namespaces with their sidecar injection status and Istio labels
-
mesh-list-services - List services in the mesh namespaces
namespace (string) - Optional namespace to filter services (default: all namespaces)
-
mesh-list-workloads - List workloads in the mesh namespaces
namespace (string) - Optional namespace to filter workloads (default: all namespaces)
-
mesh-health-check - Perform a comprehensive health assessment of the Istio service mesh including control plane and data plane status
namespace (string) - Optional namespace to focus the health check on (default: all namespaces)
-
mesh-topology - Show the mesh topology including control plane components and cluster connectivity
-
traffic-topology - Analyze the service mesh traffic topology showing service dependencies, traffic flow, and communication patterns
namespaces (string) (required) - Comma-separated list of namespaces to include in the graph, or 'all' to include all accessible mesh namespaces
-
service-troubleshoot - Investigate service errors using logs, traces, and Istio configuration to identify root causes
namespace (string) (required) - Namespace where the service is deployedservice (string) (required) - Name of the service to troubleshootworkload (string) - Optional workload or pod name to fetch logs from (if omitted, uses the service name)
-
trace-analysis - Investigate distributed traces for a service to identify latency bottlenecks, error sources, and slow spans
namespace (string) (required) - Namespace where the service is deployedservice (string) (required) - Name of the service to investigate traces for
-
istio-config-review - Review and validate Istio configuration in a namespace, checking for misconfigurations and best practice violations
namespace (string) (required) - Namespace to review Istio configuration for
-
vm-troubleshoot - Generate a step-by-step troubleshooting guide for diagnosing KubeVirt VirtualMachine issues
namespace (string) (required) - The namespace of the VirtualMachine to troubleshootname (string) (required) - The name of the VirtualMachine to troubleshoot
-
windows-golden-image - Guides creation of a Windows golden image via the KubeVirt windows-efi-installer Tekton pipeline
winImageDownloadURL (string) (required) - Microsoft Windows ISO download URL (must be https://)namespace (string) - Target namespace for the PipelineRunwindowsVersion (string) - Windows version: 10, 11, 2k22 (default), or 2k25pipelineVersion (string) - Pipeline version (default: latest). Use specific version like 0.25.0 if needed
-
hco-status - Generate a status report for the HyperConverged Cluster Operator (HCO) managing KubeVirt and related components
- pipeline-troubleshoot - Gather PipelineRun status, its Pipeline definition, TaskRuns, failed or errored step logs, warning events, Pipeline-as-Code Repository, and TektonConfig context for Tekton troubleshooting
namespace (string) (required) - Namespace of the PipelineRun to troubleshootname (string) (required) - Name of the PipelineRun to troubleshoot
Resources
Resource Templates
Helm Chart
A Helm Chart is available to simplify the deployment of the Kubernetes MCP server.
helm install kubernetes-mcp-server oci://ghcr.io/containers/charts/kubernetes-mcp-server
For configuration options including OAuth, telemetry, and resource limits, see the chart README and values.yaml.
💬 Community
Join the conversation and connect with other users and contributors:
- Slack - Ask questions, share feedback, and discuss the Kubernetes MCP server in the
#kubernetes-mcp-server channel on the CNCF Slack workspace. If you're not already a member, you can request an invitation.
🧑💻 Development
Running with mcp-inspector
Compile the project and run the Kubernetes MCP server with mcp-inspector to inspect the MCP server.
# Compile the project
make build
# Run the Kubernetes MCP server with mcp-inspector
npx @modelcontextprotocol/inspector@latest $(pwd)/kubernetes-mcp-server
mcp-name: io.github.containers/kubernetes-mcp-server