Epic Goal

• Look at areas where we can make meaningful upstream contributions to the Backstage community, specifically around the MCP server support in Backstage
• The initial MCP plugins we developed for 1.8 could serve as a good starting point, but if not, we should look at potential alternatives

Why is this important?

• Contributing back our MCP plugins would serve to provide reference implementations of MCP tools, based on the MCP server support
• Allows us to get more engaged with the Backstage community

Scenarios

1. Look into contributing the RHDH MCP tools to upstream (software-catalog-mcp-tool and techdocs-mcp-tool)
2. Look into other areas of potential community involvement
3. For any upstream plugins: Update RHDH plugin overlays and marketplace accordingly

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