Epic Goal

• track upstream Backstage community plugin requests including https://github.com/backstage/community-plugins/issues/4034 
• track any catalog entity extension work stemming from https://github.com/backstage/community-plugins/issues/4034 or https://github.com/backstage/backstage/issues/30218 that could be of use to mcp registry/catalog
• track RHOAI work in this space, as first socialized via https://docs.google.com/presentation/d/1T5iRyIJj2i_q_TCDBCw4LAIjCmQVcvePaOeLPK7CUQ0/edit?slide=id.g361314be5d1_0_0#slide=id.g361314be5d1_0_0  and https://docs.google.com/document/d/1b3rDjeWdjkWbnYMFlqeQ1uaT8iDd0Dl2AECa89I7x8g/edit?tab=t.0#heading=h.cjq598823q9 and 
• track the upstream community registry https://github.com/modelcontextprotocol/registry/tree/main 

Why is this important?

Due diligence understanding and some level of intergration / collaboration is vital on all these fronts

Approach

Monitor as task on  per sprint basis and provide reports on activity, and update related Jiras that are affected