A Model Context Protocol (MCP) server for Red Hat OpenShift Cluster Manager (OCM) API operations. Provides 30 read-only tools for cluster management, monitoring, account operations, and…
OCM MCP Server is an MCP project maintained in the judexzhu/mcp-ocm repository. The maintainer describes its purpose as “A Model Context Protocol (MCP) server for Red Hat OpenShift Cluster Manager (OCM) API operations. Provides 30 read-only tools for cluster management, monitoring, account operations…”. Read the project documentation for the complete scope.
The project provides a local client configuration using uv. Follow the repository’s build and installation steps before copying it, and replace example paths with the paths on your own computer.
The example declares RH_API_OFFLINE_TOKEN. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| ocm_get_cluster | Cluster details with HCP/Classic detection |
| ocm_search_clusters | Search clusters by name, state, region, etc. (OCM search syntax) |
| ocm_get_cluster_status | Cluster status (DNS readiness, provisioning state, health) |
| ocm_get_cluster_resources | Currently available cluster resources (CPU, memory) |
| ocm_get_cluster_machine_pools | Machine pools (Classic) or node pools (HCP) — auto-detected |
| ocm_get_cluster_service_logs | Service logs with pagination (page/size params) |
| ocm_get_cluster_install_logs | Installation logs and history |
| ocm_get_cluster_uninstall_logs | Uninstall logs |
| ocm_get_cluster_alerts | Cluster alerts with severity breakdown |
| ocm_get_cluster_operators | Operator status with condition summaries |
| ocm_get_cluster_cpu_metrics | CPU metrics by node role and OS |
| ocm_get_cluster_socket_metrics | Socket metrics by node role and OS |
| ocm_get_cluster_node_metrics | Node metrics |
| ocm_get_cluster_vpc | VPC info with subnet analysis (public/private) |
| ocm_get_cluster_ingress | Ingress configuration and DNS info |
| ocm_get_cluster_private_link | AWS Private Link configuration |
| ocm_get_cluster_identity_providers | Identity provider configuration |
| ocm_get_cluster_groups | RBAC groups and their users |
| ocm_get_cluster_addons | Installed add-ons |
| ocm_get_cluster_autoscaler | Cluster autoscaler configuration |
| ocm_get_cluster_kubelet_configs | Kubelet configurations |
| ocm_get_cluster_upgrade_policies | Upgrade policies (Classic + HCP control plane + node pool) |
| ocm_get_cluster_limited_support_reasons | Limited support reasons |
| ocm_get_cluster_inflight_checks | Inflight checks (provisioning debugging) |
| ocm_get_cluster_sts_operator_roles | STS operator IAM roles |
| ocm_get_cluster_provision_shard | Provision shard info |
| ocm_get_accounts_by_email | Account lookup by email |
| ocm_get_subscription | Subscription details |
| ocm_get_organization | Organization details |
| ocm_get_current_account | Currently authenticated user info |
{
"mcpServers": {
"ocm": {
"command": "uv",
"args": [
"--directory",
"/path/to/your/mcp-ocm",
"run",
"ocm_mcp_server.py"
],
"env": {
"RH_API_OFFLINE_TOKEN": "YOUR_RH_API_OFFLINE_TOKEN"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| RH_API_OFFLINE_TOKEN | Declared in the maintainer’s client configuration. | Check documentation |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Connect Flutter applications with AI coding assistants via the Model Context Protocol.
Enables natural language interaction with Splunk Enterprise and Cloud for searching data and managing resources.