Red Hat API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RH_SSO_URL | No | Optional custom SSO URL (default: https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/token) | https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/token |
| RH_API_BASE_URL | No | Optional custom API base URL (default: https://access.redhat.com) | https://access.redhat.com |
| RH_API_OFFLINE_TOKEN | Yes | Your Red Hat API offline token obtained from https://access.redhat.com/management/api |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_kcsA | Search for Red Hat KCS Solutions and return a list with Solution IDs. Args: query: Search query string rows: Number of results to return (default: 50) start: Starting index for pagination (default: 0) Returns: List of solutions with their IDs and metadata By default, this tool returns only documents where documentKind is either "Article" or "Solution" and accessState is either "active" or "private". |
| get_kcsA | Get a specific solution by ID and extract structured content Args: solution_id: The ID of the solution to retrieve Returns: Dictionary with title, Environment, Issue, Resolution, and Root Cause |
| search_casesB | Search for Red Hat cases and return a list of case numbers. Args: query: Search query string rows: Number of results to return (default: 10) start: Starting index for pagination (default: 0) Returns: List of cases with their numbers and metadata |
| get_caseA | Get case details by case number. Args: case_number: The case number (e.g., "01234567") Returns: Formatted case data with description, severity, issue, case number, and comments |
| get_case_rawA | Get ALL raw fields from a case for debugging/discovery. Args: case_number: The case number (e.g., "01234567") Returns: The complete unfiltered API response with all available fields |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_case_prompt | Summarize a Red Hat support case in C.A.S.E. markdown format. |
| resolve_case_prompt | Red Hat Case Resolver Agent: investigation and solution workflow for a support case. |
| resolve_case_prompt_v2 | Red Hat Case Resolver Agent: investigation and solution workflow for a support case. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: search and retrieve for KCS solutions and cases, with get_case_raw explicitly for raw debugging access. No two tools have overlapping purposes.
All tools follow a consistent verb_noun pattern using snake_case (search_kcs, get_kcs, search_cases, get_case, get_case_raw). The modifier 'raw' logically extends get_case.
Five tools provide a focused surface for Red Hat support knowledge and case retrieval, neither bloated nor sparse. Each tool serves a clear purpose in the workflow.
The tool set covers the complete read lifecycle for both KCS solutions (search, get by ID) and support cases (search, get details, raw access), with no obvious missing operations for a read-only support API.