// Module included in the following assemblies:
//
// * ai_applications/mcp_server/mcp-server-overview.adoc

:_mod-docs-content-type: PROCEDURE
[id="ai-app-mcp-server-install-helm_{context}"]
= Install the MCP server Helm chart

[role="_abstract"]
To install the Model Context Protocol (MCP) server for Red Hat {product-title} feature, install the MCP server for Red Hat {product-title} Helm chart.

.Prerequisites

* Access to OpenShift console with admin rights.

.Procedure

. Install the MCP server for Red Hat {product-title} Helm chart by running one of the following commands:
+
* For read-only access (recommended for most use cases):
+
[source,terminal]
----
$ helm upgrade -i -n openshift-mcp-server --create-namespace openshift-mcp-server \
    openshift-helm-charts/redhat-openshift-mcp-server \
    --set config.toolsets=<toolset-names> \
    --set ingress.host=<hostname> \
    --set openshift=true \
    --set-json 'rbac.extraClusterRoleBindings=[{"name":"use-view-role","roleRef":{"name":"view","external":true}}]'
----
+
* For full cluster access:
+
[source,terminal]
----
$ helm upgrade -i -n openshift-mcp-server --create-namespace openshift-mcp-server \
    openshift-helm-charts/redhat-openshift-mcp-server \
    --set config.toolsets=<toolset-names> \
    --set ingress.host=<hostname> \
    --set openshift=true \
    --set-json 'rbac.extraClusterRoleBindings=[{"name":"admin-access","roleRef":{"name":"cluster-admin","external":true}}]'
----

* Where `<hostname>` is a fully qualified domain name (FQDN) that serves as the entry point for the {product-title} MCP server. This host address is used by the Ingress controller to route external traffic to the MCP server service. This should be a URL such as `mcp-server.apps.cluster-name.domain.com`.

* Where `<toolset-names>` can include toolsets from the following table.
+
.Available toolsets
|===
|Toolset |Description |Default |Status

|`core`
|Most common tools for Kubernetes management (Pods, Generic Resources, Events, etc.)
|Yes
|Technology Preview

|`config`
|View and manage the current local Kubernetes configuration (kubeconfig)
|Yes
|Technology Preview

|`netedge` 
|NetEdge troubleshooting tools for {product-title} 
|No
|Technology Preview

|`helm`
|Tools for managing Helm charts and releases
|No
|Technology Preview

|`metrics`
|Toolset for querying Prometheus and Alertmanager endpoints in efficient ways
|No
|Technology Preview

|`ossm`
|Most common tools for managing OSSM
|No
|Technology Preview

|`kubevirt`
|KubeVirt virtual machine management tools
|No
|Developer Preview

|`tekton`
|Tekton pipeline management tools for Pipelines, PipelineRuns, Tasks, and TaskRuns
|No
|Developer Preview
|===


.Verification

The command returns output similar to the following:

.Example
[source,terminal]
----
Release "openshift-mcp-server" does not exist. Installing it now.
NAME: openshift-mcp-server
LAST DEPLOYED: Mon Apr 20 09:28:13 2026
NAMESPACE: openshift-mcp-server
STATUS: deployed
REVISION: 1
TEST SUITE: None
----
