OpenShift Lightspeed & MCP Gateway
OpenShift Lightspeed (OLS) is an AI assistant integrated into the OpenShift web console. Combined with the MCP Gateway (a Kuadrant community extension), it can execute cluster operations through AI-callable tools.
Click to explore the MCP Gateway graph with 5 servers and 55 tools — drag to rotate
Accessing OpenShift Lightspeed
-
Log in to the OpenShift Console at
https://console-openshift-console.apps.cluster.example.com -
Click the Lightspeed icon in the console header (chat bubble icon).
-
Ask questions about your cluster, workloads, or Kubernetes concepts.
Architecture: OLS + MCP Gateway
graph TB
USER[Platform Engineer] -->|Chat| OLS[OpenShift Lightspeed]
OLS -->|LLM Inference| LLM[LLM Model Server]
OLS -->|Streamable HTTP| MCPGW[MCP Gateway]
subgraph MCP_Servers[MCP Servers - 55 Tools]
K8S[k8s-mcp-server - 22 tools]
OCPS[ocp-mcp-server - 19 tools]
ARGO[argocd-mcp-server - 14 tools]
end
OLS -->|Direct SSE| RHDH[rhdh-mcp-server - 7 tools]
MCPGW --> K8S
MCPGW --> OCPS
MCPGW --> ARGO
K8S -->|kubectl| CLUSTER[OpenShift API]
OCPS -->|oc| CLUSTER
ARGO -->|REST API| ARGOCD[ArgoCD Server]
RHDH --> DEVHUB[Developer Hub]
MCP Tools Reference — 55 Tools
The MCP Gateway federates 55 tools from 4 backend MCP servers, plus 7 from Developer Hub accessed directly. Each tool is callable by the LLM through natural language prompts.
Kubernetes Tools (prefix k8s — 22 tools)
| Tool Name | Description |
|---|---|
|
List all pods across the cluster |
|
List pods in a specific namespace |
|
Get details of a specific pod |
|
Get logs from a pod |
|
Show resource usage for pods |
|
Run a pod with a given image |
|
Execute a command inside a pod |
|
Delete a pod |
|
List resources by kind in a namespace |
|
Get a specific resource by name |
|
Create or update a resource from YAML |
|
Delete a specific resource |
|
Scale a deployment/statefulset |
|
List all namespaces |
|
List all OpenShift projects |
|
Show resource usage for nodes |
|
Get logs from a node |
|
Get stats summary from a node |
|
List events in a namespace |
|
Install a Helm chart |
|
List Helm releases |
|
Uninstall a Helm release |
Example Prompts
-
"List all pods in the neuralbank-stack namespace" →
k8spods_list_in_namespace -
"Show me the logs of the neuralbank-backend pod" →
k8spods_log -
"What events happened in user1-neuralbank?" →
k8sevents_list -
"Scale the frontend deployment to 3 replicas" →
k8sresources_scale -
"Install Redis using Helm in my namespace" →
k8shelm_install -
"Show me node resource usage" →
k8snodes_top
OpenShift Tools (prefix ocp — 19 tools)
| Tool Name | Description |
|---|---|
|
Create a new Deployment |
|
Deploy a database (Redis, PostgreSQL, etc.) |
|
Create a Kubernetes Service |
|
Create a Horizontal Pod Autoscaler |
|
Create a NetworkPolicy |
|
Monitor all deployments in a namespace |
|
Detect resource issues (OOMKill, pending pods) |
|
Check overall cluster health |
|
Check node conditions (Ready, Pressure) |
|
Check kubelet status on nodes |
|
Check CRI-O container runtime status |
|
Get cluster performance metrics |
|
Analyze journalctl for pod errors |
|
Analyze pod disruption budgets |
|
Run a CPU stress test |
|
Run a network connectivity test |
|
Run a storage I/O benchmark |
|
Run a database benchmark |
|
Run kube-burner load test |
Example Prompts
-
"Deploy a Redis database in my namespace" →
ocpdeployDatabase -
"Check the cluster health" →
ocpcheckClusterHealth -
"Are there any pods with resource issues?" →
ocpdetectResourceIssues -
"Create a HorizontalPodAutoscaler for my backend" →
ocpcreateHpa -
"Run a network test between my services" →
ocprunNetworkTest -
"Monitor all deployments in neuralbank-stack" →
ocpmonitorDeployments
ArgoCD Tools (prefix argo — 14 tools)
| Tool Name | Description |
|---|---|
|
List all ArgoCD applications (supports search, pagination) |
|
List clusters registered with ArgoCD |
|
Get full details of an application |
|
Get the resource tree (all child resources) |
|
Get managed resources with filters (kind, namespace) |
|
Get logs from workloads managed by an app |
|
Get application-level events |
|
Get events for a specific managed resource |
|
Get YAML manifests of managed resources |
|
List available actions on a resource (restart, etc.) |
|
Create a new ArgoCD application |
|
Update an existing application |
|
Delete an ArgoCD application |
|
Trigger a sync (supports dry-run, prune, revision) |
|
Execute an action on a managed resource |
Example Prompts
-
"List all ArgoCD applications" →
argolist_applications -
"Which applications are out of sync?" →
argolist_applications+ filter -
"Sync the developer-hub application" →
argosync_application -
"Show me the resource tree for the showroom app" →
argoget_application_resource_tree -
"Why is the mcp-gateway app failing?" →
argoget_resource_events+argoget_application_workload_logs -
"Restart the workshop-registration deployment" →
argorun_resource_action -
"Show me the managed resources of type Deployment in ols" →
argoget_application_managed_resources -
"Get the events for the mcp-gateway application" →
argoget_application_events
Developer Hub / Backstage Tools (no prefix — 7 tools, direct SSE)
These tools connect OLS directly to Red Hat Developer Hub (not through the Kuadrant Gateway):
| Tool Name | Description |
|---|---|
|
List and search Software Templates in the catalog |
|
List/search catalog entities (Components, APIs, Systems) |
|
Register new entities from a URL |
|
Remove registered entities |
|
List entities with TechDocs documentation |
|
Get documentation coverage statistics |
|
Retrieve TechDocs content for a specific entity |
Example Prompts
-
"List all Software Templates available in Developer Hub" →
fetch-template-metadata -
"Show me all registered components" →
fetch-catalog-entities -
"What entities have TechDocs?" →
fetch-techdocs -
"Register a new entity from https://gitea.example.com/catalog-info.yaml" →
register-catalog-entities
What is MCP (Model Context Protocol)?
MCP is an open standard that allows AI models to interact with external tools securely:
-
Tools — Functions the AI can call (e.g., list pods, sync ArgoCD apps)
-
Resources — Data the AI can read (e.g., cluster state, catalog entities)
-
Prompts — Pre-built conversation templates
-
Transports — Streamable HTTP (Kuadrant Gateway) or SSE (Developer Hub direct)
The MCP Gateway acts as a federation layer, aggregating multiple MCP servers behind a single endpoint with unified authentication via Kuadrant.
OLS Configuration
OpenShift Lightspeed connects to MCP servers through its OLSConfig custom resource:
apiVersion: ols.openshift.io/v1alpha1
kind: OLSConfig
metadata:
name: cluster
spec:
featureGates:
- MCPServer
mcpServers:
- name: mcp-gateway
url: "http://mcp-gateway-istio.mcp-system.svc:8080/mcp"
timeout: 120
- name: rhdh-catalog
url: "http://backstage-developer-hub.developer-hub.svc.cluster.local/api/mcp-actions/v1"
timeout: 120
headers:
- name: Authorization
valueFrom:
type: secret
secretRef:
name: rhdh-mcp-token
MCP Gateway Registration
Each backend MCP server is registered with the Kuadrant MCP Gateway:
apiVersion: mcp.kuadrant.io/v1alpha1
kind: MCPServerRegistration
metadata:
name: argocd-mcp-server
namespace: mcp-system
spec:
targetRef:
name: argocd-mcp-server-route
toolPrefix: argo
path: /mcp
The toolPrefix ensures tool names don’t collide across servers (e.g., argolist_applications vs k8spods_list).
ArgoCD MCP Server
The ArgoCD MCP server (argoproj-labs/mcp-for-argocd) runs on the Red Hat certified ubi9/nodejs-22 image and uses Streamable HTTP transport:
image: registry.redhat.io/ubi9/nodejs-22:latest
command: ["npx"]
args: ["argocd-mcp@latest", "http"]
env:
- name: ARGOCD_BASE_URL
value: "https://openshift-gitops-server.openshift-gitops.svc.cluster.local"
- name: ARGOCD_API_TOKEN
valueFrom:
secretKeyRef:
name: argocd-mcp-token
key: ARGOCD_API_TOKEN
Customer Service MCP
The workshop also deploys a Customer Service MCP as part of the Neuralbank stack. This MCP server exposes backend operations (customer CRUD, credit scoring) as AI-callable tools:
# Check MCP server tools endpoint
curl -s -H "X-API-Key: $API_KEY" \
"https://user1-customer-service-mcp.apps.cluster.example.com/tools" \
| python3 -m json.tool
Summary
OpenShift Lightspeed with the MCP Gateway provides 55 federated tools across 5 MCP servers:
| Server | Prefix | Tools |
|---|---|---|
k8s-mcp-server |
|
22 |
ocp-mcp-server |
|
19 |
argocd-mcp-server |
|
14 |
rhdh-mcp-server |
(none) |
7 |
customer-svc-mcp |
(app) |
varies |
This transforms the OpenShift console into an AI-powered operations center where platform engineers can manage Kubernetes resources, ArgoCD applications, Developer Hub catalog, and business services — all through natural language.