Skip to content Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.
Product
Directory
Developers
Company
MCP Server Rhoai Workbenches MCP server | PlugMCP
Skip to content From the publisher
Documentation MCP Server for Red Hat OpenShift AI
This project implements a Model Context Protocol (MCP) server for managing Red Hat OpenShift AI (RHOAI) workbenches. It provides tools for listing, creating, and managing workbenches, images, hardware profiles, and storage in OpenShift clusters, also it provides tools for monitoring resource consumption by workbenches per user, workbench, namespace or cluster.
This project is part of a Bachelor's thesis.
Prerequisites
This project is meant as a bachelors thesis about MCP servers in RHOAI
Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.
Product
Directory
Developers
Company
Go 1.24.0 or later
Access to an OpenShift cluster with RHOAI installed
oc CLI logged in to your cluster
(Optional) golangci-lint for code linting
Installation git clone https://github.com/amaly/mcp-server-rhoai.git
cd mcp-server-rhoai
Ensure you're logged in to your OpenShift cluster:
oc login <your-cluster-url>
Building The project includes a Makefile for easy building:
Build with Make # Build with linting and testing (recommended)
make build
# Build without running lint and tests (faster)
go build -o mcp-server-rhoai
Run linting checks (golangci-lint)
Execute all tests
Compile the binary as mcp-server-rhoai
Build Outputs
Binary location: ./mcp-server-rhoai
Testing The project has a comprehensive unit test suite (60 tests across 7 test files) covering every tool module. Tests use Kubernetes fake clients (dynamicfake.NewSimpleDynamicClient) and function-variable mocking to isolate logic from live cluster dependencies, so no running cluster is needed.
Run tests using Make or directly with Go:
# Run all tests with Make
make test
# Run tests directly with verbose output
go test -v ./tools/... ./resources/... ./prompts/...
Workbench tools — CRUD operations, status transitions, and helper functions (image tag parsing, resource extraction, PVC name resolution)
Storage tools — PVC creation, deletion, and size updates including rejection of size decreases
Image tools — Custom image CRUD, default-image and in-use protection checks, image listing
Hardware profile tools — Profile CRUD and resource identifier parsing
Resource consumption tools — Value parsing (millicores, Gi suffixes, decimals), aggregation, and per-workbench/namespace/user/cluster queries
Namespace & pod tools — Listing and filtering by namespace
Each tool module has a dedicated *_test.go file with both success and error-path cases. Table-driven subtests are used where multiple input variations need to be verified.
Evaluation Uses Promptfoo for testing tool selection accuracy.
Run Evaluation export GOOGLE_API_KEY=your-key-here
make eval # run tests
make eval-view # run and open results in browser
What It Tests
Tool selection - correct tool called for each prompt
Parameter extraction - arguments passed correctly (namespace, workbench name, etc.)
Key Learnings Tool descriptions must be explicit for model-agnostic compatibility:
Mark optional fields with omitempty and describe defaults in jsonschema descriptions
Include valid values in descriptions (e.g., "status: 0 for running, 1 for stopped")
Simpler models (Gemini Flash) are stricter than Claude - good for testing robustness
Configuration The MCP server can be configured in AI assistants to enable workbench management through natural language.
VSCode/Cursor Setup
Open MCP Settings in Cursor:
Press Ctrl + Shift + P (Windows/Linux) or Cmd + Shift + P (Mac)
Type "Open MCP Settings"
Click "New MCP server"
Add configuration:
Read-only mode (default, safer):
{
"mcpServers": {
"mcp-server-rhoai": {
"command": "/home/amaly/mcp-server-rhoai/mcp-server-rhoai"
}
}
}
Read-write mode (full access):
{
"mcpServers": {
"mcp-server-rhoai": {
"command": "/home/amaly/mcp-server-rhoai/mcp-server-rhoai",
"env": {
"MCP_RHOAI_MODE": "write"
}
}
}
}
Verify installation:
Check that the server is enabled in Cursor MCP settings
You should see available tools listed
Start using:
Ask the AI assistant: "List all workbenches in namespace mcp-test"
Or: "Show me resource consumption per namespace"
Claude Desktop Setup
Locate Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
Edit the config file and add the MCP server:
Read-only mode (default):
{
"mcpServers": {
"mcp-server-rhoai": {
"command": "/home/amaly/mcp-server-rhoai/mcp-server-rhoai"
}
}
}
Read-write mode (full access):
{
"mcpServers": {
"mcp-server-rhoai": {
"command": "/home/amaly/mcp-server-rhoai/mcp-server-rhoai",
"env": {
"MCP_RHOAI_MODE": "write"
}
}
}
}
Restart Claude Desktop for changes to take effect
Verify connection:
Look for the MCP connection indicator in Claude Desktop
Ask Claude: "What workbenches are available in my cluster?"
Important Notes Permissions: The MCP server uses your current oc login credentials. All operations are performed with your user's permissions.
Security: Start with read-only mode to explore safely. Only enable write mode when you need to create or modify resources.
Tool Modes The server supports two operation modes for safety and flexibility:
Read-Only Mode (Default) Only listing and querying tools are available. This mode is safer and prevents accidental modifications to your cluster.
List workbenches, images, hardware profiles, PVCs
Query resource consumption
View namespace and pod information
Read-Write Mode All tools are available, including create, delete, and modify operations.
Create/Delete workbenches
Create/Delete custom images
Create/Delete hardware profiles
Create PVCs
Start/Stop workbenches
Configuring the Mode The mode can be set via command-line flag or environment variable:
Command-line flag (recommended for promptfoo/scripts):
./mcp-server-rhoai -mode write
Environment variable (for MCP client configs):
export MCP_RHOAI_MODE=write
The -mode flag takes precedence over the environment variable.
Available Tools
Read-Only Tools (Always Available)
List Pods - List pods in a namespace
List Namespaces - List all namespaces in the cluster
List Workbenches - List workbenches in a specific namespace
List All Workbenches - List workbenches across all namespaces
List Images - List all available notebook images
List Hardware Profiles - List available hardware profiles
List PVCs - List persistent volume claims in a namespace
List Resource Consumption Per Workbench - Get resource usage for a specific workbench
List Resource Consumption Per Namespace - Get resource usage for all workbenches in a namespace
List Resource Consumption Per User - Get resource usage for a specific user
List Resource Consumption Per Cluster - Get cluster-wide resource usage
Write Tools (Only in Write Mode)
Create Workbench - Create a new workbench with specified configuration
Delete Workbench - Delete an existing workbench
Change Workbench Status - Start or stop a workbench
Create Custom Image - Create a custom notebook image
Delete Image - Delete a custom image
Create Hardware Profile - Create a new hardware profile
Delete Hardware Profile - Delete a hardware profile
Create PVC - Create a persistent volume claim
Development
Project Structure mcp-server-rhoai/
├── main.go # Entry point
├── core/ # Shared types and utilities
│ ├── gvr.go # Kubernetes GroupVersionResource definitions
│ ├── common_types.go # Shared output/namespace types
│ ├── workbench_types.go # Workbench-related types
│ ├── image_types.go # Image-related types
│ ├── hardware_profile_types.go # Hardware profile types
│ ├── pvc_types.go # PVC-related types
│ ├── resource_consumption_types.go # Resource consumption types
│ └── logging.go # Logging utilities
├── tools/ # MCP tool implementations
│ ├── registry.go # Tool registration (read-only & write modes)
│ ├── workbench_tools.go # Workbench CRUD & status tools
│ ├── image_tools.go # Image management tools
│ ├── hardware_profile_tools.go # Hardware profile tools
│ ├── storage_tools.go # PVC management tools
│ ├── namespace_tools.go # Namespace listing tools
│ ├── pod_tools.go # Pod listing tools
│ ├── resource_consumption_tools.go # Resource monitoring tools
│ └── common.go # Shared tool helpers
├── resources/ # MCP resource definitions
├── prompts/ # MCP prompts
└── Makefile # Build automation
Adding New Tools
Implement the tool function in the appropriate file in tools/
Register it in tools/registry.go:
For read-only: Add to RegisterReadOnlyTools()
For write: Add to RegisterWriteTools()
Add tests in tools/*_test.go
Update this README
Linting
Install golangci-lint go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest
Run Linting
Directory score 5/100 Listed 10 of 10
In the official MCP Registry 0 of 18
Claimed by its maintainer 0 of 8
Answers with a tool list 0 of 12
GitHub stars 3 of 16
Weekly downloads 0 of 10
Public Apis A collective list of free APIs Pipeworx Gateway Live data for AI agents. 250+ data sources, 900+ tools. Ask questions in plain English with ask_pipeworx — trade flows, SEC filings, drug safety, housing data, and more. No API keys needed. Rea Reverse engineer anything with agents, from app behavior down to native binaries. Coding Interview University A complete computer science study plan to become a software engineer. Skills Skills for Real Engineers. Straight from my .agents directory. Hermes Agent The agent that grows with you SparkForge Access a versatile collection of tools for media generation, web scraping, and cryptocurrency research. Convert between data formats, summarize long documents, and extract text from images or PDFs wit N8n Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations. Awesome Go A curated list of awesome Go frameworks, libraries and software Ohmyzsh 🙃 A delightful community-driven (with 2,500+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python Agency Agents A complete AI agency at your fingertips - From frontend wizards to Reddit community ninjas, from whimsy injectors to reality checkers. Each agent is a specialized expert with personality, processes, a The Art Of Command Line Master the command line, in one page agent-browser Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web a azure-aigateway Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: semantic caching, token limit, content safety, load balancing, AI model governance, MCP rate limiting, jailb
No tool list yet. Remote servers get one after the first health check.
How do I install MCP Server Rhoai Workbenches? Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does MCP Server Rhoai Workbenches need an API key? No required environment variable is listed on this record.
What transport does MCP Server Rhoai Workbenches use? MCP Server Rhoai Workbenches runs locally over stdio.
When was MCP Server Rhoai Workbenches last checked? Last checked 2026-10-27. This project is meant as a bachelors thesis about MCP servers in RHOAI
azure-compute Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine l Tools have descriptions 0 of 6