-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Creation of MCP Extras Framework
-
False
-
-
False
-
To Do
-
RHDHPLAN-391 - [MCP] Strategy: Adopt Upstream MCP Actions & Establish 'Extras' Incubation Layer
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
-
EPIC Goal
Given specific RHDH features that do not yet exist upstream (e.g., specific Catalog filters or advanced Scaffolder actions), When migrating the code, Then these features must be packaged into new plugins within the redhat-developer repository, following the naming convention rhdh-mcp-<domain>-extras (e.g., rhdh-mcp-software-catalog-extras).
Background/Feature Origin
As part of RHDHPLAN-391, we're moving towards an upstream first process in terms of consuming MCP tools in RHDH. However, there may be scenarios where we need to include MCP tools in a release of RHDH, that have not yet been merged upstream (or in some scenarios, can't be upstreamed).
The "extras" framework will enable us to deliver plugins in a release of RHDH which will provide overlays on top of the community plugins that provide MCP tools.
Why is this important?
This will enable us to still prioritize upstream first when writing MCP tools, but still provide an environment/method to deliver MCP tools in a release of RHDH, while we wait on the MCP tool(s) to be delivered/merged upstream
User Scenarios
Dependencies (internal and external)
Acceptance Criteria
- Migrate the remaining tools in mcp-integrations to the “-extras” plugins framework
- For any tools that do not have an upstream replacement
- Determine if any new tools in 1.10 need inclusion in the MCP overlays (e.g. scaffolder, or notebook)
- Implementation of the overlay pattern
- The MCP extras plugins should not conflict with any upstream tools in RHDH and must be deployable alongside it
- Updated marketplace entries for the extras overlays
- Updated RHDH plugin exports for the extras overlays
Release Enablement/Demo - Provide necessary release enablement details
and documents
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>