Red Hat API MCP Server
Related Servers
Alternatives to Red Hat API MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for Redmine project management, enabling tools for managing projects, issues, users, time entries, groups, memberships, versions, wiki, news, attachments, search, and Agile sprints via the Redmine REST API.8921 npm1MIT
- FlicenseNot gradedqualityDmaintenanceFastMCP server that enables AI assistants to integrate with Red Hat Errata Tool, allowing access to product information and advisory details through authenticated API calls.-
- FlicenseNot gradedqualityCmaintenanceMCP server for ticketing automation that exposes tools to create, search, and update IT helpdesk tickets, with metrics tracking.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to interact with Red Hat OpenShift AI environments, providing tools for project management, workbench operations, model serving, and more.9MIT
- -licenseNot gradedqualityBmaintenanceA vendor-agnostic MCP server for technical support engineers, providing knowledge search, ticket analysis, and resolution suggestions.-
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server suite for Red Hat's automation ecosystem, enabling AI assistants to interact with Ansible Automation Platform, Event-Driven Ansible, ansible-lint, and official Red Hat documentation with secure domain validation.33MIT
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.