Overview

Phase 1 of the MCP (Model Context Protocol) server integration for the RBAC service. This epic covers the initial read-only integration that enables the HCC AI assistant to query RBAC data via MCP tools.

Related feature: CRCPLAN-420 - MCP-based agent for RBAC

Goal

Deliver a working MCP server for the RBAC service that integrates with the HCC AI agent service. In Phase 1, only read-only mode is supported.

Scope

• All existing GET endpoints are exposed as MCP tools.
• Additional tools (write operations, advanced queries) will be added in following phases based on testing and feedback.

Deployment Constraints

• The MCP server is enabled in stage only until further notice.
• The MCP endpoint is not accessible via the gateway. It is only accessible internally within the cluster.

Acceptance Criteria

• RBAC MCP server is running and reachable internally in stage.
• All existing GET endpoints are available as MCP tools.
• The HCC AI agent service can successfully discover and invoke RBAC MCP tools.
• No write operations are exposed in this phase.
• The MCP endpoint is not routable from the external gateway.
• Servers must follow the RH guidelines and rules: https://docs.google.com/document/d/1QqUdBR3w3SNmiUR9xLEgt8_TGfUqgqzH-_2TSUg0DkU/edit?usp=sharing