Red Hat Lightspeed MCP
OfficialRelated Servers
Alternatives to Red Hat Lightspeed MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for OSIDB (Red Hat Product Security's vulnerability management system). Enables read-only querying of flaws, affects, trackers, and status via natural language from MCP clients like Cursor or Claude Desktop.2MIT
- AlicenseBqualityDmaintenanceEnterprise-grade MCP server exposing Ansible Automation Platform 2.x as a complete AI interface for LLMs, enabling natural language management of automation resources.861Apache 2.0
- 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.35MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with any REST API that has an OpenAPI specification by providing a lightweight MCP server that translates between natural language and API calls.MIT
- AlicenseAqualityCmaintenanceMCP server that exposes Ansible modules to AI agents with a search-schema-check-execute workflow, enabling safe ad-hoc runs via check mode by default. It provides tools to search modules, fetch schemas, run modules, and list collections.53Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for the Red Hat Advanced Cluster Security for Kubernetes API, providing LLM access to all 69 API services and 361 endpoints through six meta-tools for discovery, inspection, and direct API calls.Apache 2.0
TDQS
Scored across 51 tools
Several tool families overlap heavily: vulnerability dashboard vs raw CVE list tools, planning lifecycle vs 'relevant' lifecycle/appstream tools, and advisor rule content/details/active-rules/search tools. The descriptions give useful preference guidance, but with 51 tools the boundaries are still easy to confuse, especially across domains with similar list/get/get_details patterns.
Most tools follow a predictable service__verb_noun pattern such as inventory__list_hosts, vulnerability__get_cves, and planning__get_rhel_lifecycle. There are minor deviations like load_cve_dashboard, find_host_by_name, and the unprefixed get_mcp_version, but overall the convention is readable and consistent.
The server exposes 51 tools across many distinct Red Hat services, which is a very large surface for an agent to navigate reliably. Several domains contain redundant dashboard/raw or catalog/relevant variants, so the count feels heavy rather than tightly scoped.
Coverage is strong for read/analysis workflows in inventory, vulnerability, advisor, and planning, but other domains are partial: content-sources only lists and gets repositories, image-builder lacks create/update/delete operations, and there is no broad remediation action surface. These gaps are workable for read-only insights but leave notable holes in lifecycle/management coverage.