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 | https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/token |
| RH_API_BASE_URL | No | Optional custom base URL for Red Hat API | https://access.redhat.com |
| RH_API_OFFLINE_TOKEN | Yes | Your Red Hat API offline token |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_kcsB | Search for Red Hat KCS Solutions and return a list with Solution IDs. |
| get_kcsA | Get a specific solution by ID and extract structured content |
| search_casesB | Search for Red Hat cases and return a list of case numbers. |
| get_caseC | Get case details by case number. |
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 4 tools
Each tool targets a distinct action-resource pair: search vs get, and KCS vs cases. There is no overlapping or ambiguous functionality between the four tools.
All tool names follow a consistent verb_noun snake_case pattern, using search_ or get_ prefixes. The naming makes the purpose of each tool immediately clear.
With four tools covering two resource types, the server is tightly scoped and every tool earns its place. This is an appropriate size for a focused Red Hat support API integration.
The server provides both search and detail retrieval for KCS solutions and cases, which covers the core read-only workflow for this domain. There are no obvious gaps that would leave an agent unable to accomplish a typical KCS or case lookup task.