OpenShift LightSpeed MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OLS_API_URL | No | OpenShift LightSpeed API endpoint | http://localhost:8080 |
| OLS_TIMEOUT | No | Request timeout in seconds | 30.0 |
| OLS_API_TOKEN | No | Bearer token for authentication (required for most deployments) | |
| OLS_VERIFY_SSL | No | SSL certificate verification | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| openshift-lightspeedB | Query OpenShift LightSpeed for assistance with OpenShift, Kubernetes, and related technologies |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap, making disambiguation perfect.
A single tool name cannot be inconsistent; it follows its own pattern, so consistency is perfect.
One tool is too few for a server presumably handling OpenShift and Kubernetes queries; the scope feels thin and limiting for agents.
Only a generic query tool exists, with no support for specific operations (e.g., listing, creating, updating resources), so the surface is severely incomplete.