Epic Goal

• Establish a complete build and release pipeline and distribution strategy for the MCP Tool Plugins to ensure successful adoption and deployment
• Contribute MCP plugins to the appropriate upstream or downstream repository with proper build processes and community integration
• Publish production-ready OCI plugins that are compatible with RHDH 1.8 and Backstage 1.40+

Scenarios

1. Contribute MCP plugins to source repository
   • Find an appropriate home for the MCP Tools, whether its backstage/community-plugins (as an upstream contribution), redhat-developer/rhdh-plugins, and ensure build process is set up for plugin(s).
2. Publish OCI plugins for MCP tool(s)
   • The OCI plugins that contain the MCP tools should be deployable as an OCI-based dynamic plugin in RHDH. It should be compatible with RHDH 1.8, running Backstage 1.40 or later.
3. MCP Tool Announcement / Blog post
   • Blog post on developer.redhat.com announcing MCP tools, what they can do, and how to use them
   • Note: This may be tracked in its own, separate item

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment