Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"rosa-hcp": {
"url": "http://your-server:8080/sse",
"headers": {
"X-OCM-OFFLINE-TOKEN": "your-token-here"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server for ROSA HCP (Red Hat OpenShift Service on AWS using Hosted Control Planes) that enables AI assistants to integrate with Red Hat Managed OpenShift services.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud / devops
MCP server for using the GitLab API
MCP Server for GCP environment for interacting with various Observability APIs.
⚡ A Simple / Speedy / Secure Link Shortener with Analytics, 100% run on Cloudflare.
MCP server for Datto SaaS Protection — M365/GWS backups, restores, seats.
MCP Security Weekly
Get CVE alerts and security updates for Rosa Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for ROSA HCP (Red Hat OpenShift Service on AWS using Hosted Control Planes) that enables AI assistants to integrate with Red Hat Managed OpenShift services.
whoami, get_clusters, get_cluster, create_rosa_hcp_cluster, get_rosa_hcp_prerequisites_guide, setup_htpasswd_identity_providergit clone https://github.com/tiwillia/rosa-mcp-go
cd rosa-mcp-go
make build
# Build container image
make container-build
# Run with SSE transport
make container-run
# Deploy to OpenShift
make deploy
# Configure template parameters as needed:
# - IMAGE: Container image (default: quay.io/redhat-ai-tools/rosa-mcp-server)
# - MCP_HOST: Hostname for the route
# - CERT_MANAGER_ISSUER_NAME: TLS certificate issuer
rosa-mcp-server [flags]
Flags:
--config string path to configuration file
--host string host for SSE transport (default "0.0.0.0")
--ocm-base-url string OCM API base URL (default "https://api.openshift.com")
--ocm-client-id string OCM client ID (default "cloud-services")
--port int port for SSE transport (default 8080)
--sse-base-url string SSE base URL for public endpoints
--transport string transport mode (stdio/sse) (default "stdio")
ocm_base_url = "https://api.openshift.com"
transport = "stdio"
port = 8080
sse_base_url = "https://example.com:8080"
Stdio transport requires the OCM_OFFLINE_TOKEN environment variable for authentication.
# Set your OCM token
export OCM_OFFLINE_TOKEN="your-ocm-token-here"
# Start server
./rosa-mcp-server --transport=stdio
SSE transport uses header-based authentication with the X-OCM-OFFLINE-TOKEN header. No environment variables required.
# Start SSE server
./rosa-mcp-server --transport=sse --port=8080
# Server will be available at:
# - SSE stream: http://localhost:8080/sse
# - MCP messages: http://localhost:8080/message
# Authentication: Send X-OCM-OFFLINE-TOKEN header with requests
If you already have the ocm-cli: Run ocm token --refresh to obtain your offline token.
For stdio transport:
export OCM_OFFLINE_TOKEN="your-token-here"
For SSE transport: Include header in HTTP requests:
X-OCM-OFFLINE-TOKEN: your-token-here
Get information about the authenticated account.
{
"name": "whoami",
"description": "Get the authenticated account"
}
Retrieve a list of clusters filtered by state.
{
"name": "get_clusters",
"parameters": {
"state": {
"type": "string",
"description": "Filter clusters by state (e.g., ready, installing, error)",
"required": true
}
}
}
Get detailed information about a specific cluster.
{
"name": "get_cluster",
"parameters": {
"cluster_id": {
... [View full README on GitHub](https://github.com/redhat-community-ai-tools/rosa-mcp-server#readme)