Model Context Protocol server for Red Hat Lightspeed - advisor, image builder, inventory, and more
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"lightspeed-mcp": {
"url": "http://localhost:8000/mcp",
"type": "http",
"headers": {
"lightspeed-client-id": "",
"lightspeed-client-secret": ""
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Model Context Protocol server for Red Hat Lightspeed - advisor, image builder, inventory, and more
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops / cloud
MCP server for using the GitLab API
MCP Server for GCP environment for interacting with various Observability APIs.
Enhanced MCP server for GitLab: group projects listing and activity tracking
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
MCP Security Weekly
Get CVE alerts and security updates for io.github.RedHatInsights/insights-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
(formerly known as Insights MCP)
Red Hat Lightspeed Model Context Protocol (MCP) server is a lightweight, self-hosted solution that connects LLM-based agents - such as Claude Desktop and other MCP-compatible tools - to Red Hat Lightspeed services.
--all-tools to enable write tools (e.g. create blueprints, run composes). RBAC permissions can also restrict access.Note: Authentication is only required for accessing Red Hat Lightspeed APIs. The MCP server itself does not require authentication.
There are two ways to authenticate:
Authorization: Bearer <token> HTTP header (SSE/HTTP transports only).Client ID and Client secret for later.LIGHTSPEED_CLIENT_ID and LIGHTSPEED_CLIENT_SECRET.Different toolsets require specific roles for your service account:
RHEL Advisor viewerInventory Hosts viewerVulnerability viewer, Inventory Hosts viewerRemediations userBy default, service accounts have no access. An organization administrator must assign permissions. The MCP server will only be able to perform tasks that it has permission to perform. For example, if the user wants to allow read-only operations and deny write operations, this can be accomplished via the permissions system.
For detailed step-by-step instructions, see this video tutorial: Service Account Permissions Setup
Log in as Organization Administrator with User Access administrator role
Navigate to User Access Settings: Click Settings (⚙️ Gear Icon) → "User Access" → "Groups"
Assign permissions (choose one option):
Option A - Create New Group:
mcp-service-accounts)Option B - Use Existing Group:
Your service account will inherit all roles from the assigned group.
If you start this MCP server locally (with podman or docker) make sure the conta