Assisted Service MCP Server

What is Assisted Service MCP Server?

A Model Context Protocol server that interacts with the OpenShift assisted installer API. It helps diagnose cluster failures and find fixes. Designed for developers and cluster administrators working with OpenShift installations.

How to use Assisted Service MCP Server?

Obtain an OpenShift API token from https://cloud.redhat.com/openshift/token. Start the server using STDIO configuration (e.g., in VSCode) or SSE transport (recommended). Provide the token as the OFFLINE_TOKEN environment variable or as an OCM-Offline-Token request header for SSE.

Key features of Assisted Service MCP Server

• List, create, and manage assisted installer clusters
• Retrieve detailed cluster and infraenv information
• Monitor cluster and host events
• Set cluster VIPs and host roles
• List OpenShift versions and operator bundles

Use cases of Assisted Service MCP Server

• Diagnose cluster installation failures via events
• Automate cluster creation and installation triggers
• Configure infrastructure environments for new clusters
• Manage host roles during cluster setup

FAQ from Assisted Service MCP Server

How do I get an API token?

Go to https://cloud.redhat.com/openshift/token to obtain your offline token.

What transport options are available?

STDIO (for VSCode-like clients) and SSE (recommended). Provide configuration JSON with the appropriate transport, URL, and token.

Can I pass the token via request header?

Yes. For SSE, add the OCM-Offline-Token header instead of setting the OFFLINE_TOKEN environment variable.

What tools does the server expose?

Tools span cluster management (list, info, create, install, set VIPs), events (cluster, host), infraenv info, host role setting, and OpenShift version/operator listing and adding.

Are there any known limits?

—