Background

One of the motivators for upstreaming the connector was the spotify maintainer RFC https://github.com/backstage/backstage/issues/32062 aimed at aligning the community on how MCP Servers were modeled into the catalog

The discussion details in many ways mirrored / paralleled the discussion RHDH AI had internally around modeling AI Models and AI Model Servers into the catalog.

As such, although not exact matches per se, there is notable conceptual overlap between modeling MCP servers (and by extension, MCP registries and MCP tools) and AI models, model servers, and model registries.

Recent SIG calls have some early feedback that were captured in the owning epic https://issues.redhat.com/browse/RHIDP-11685 

Task particulars

After the creation of the RFC in RHIDP-11754, both 

• curate direct interaction posted in the RFC issue
• socialize in the Framework SIG and facilitate collaboration toward the making of decisions, formulating next steps

Where those next steps/conclusions include

• the reaching of consensus on the catalog mapping
• will a BEP be required per the Jan Framework SIG
• any clarification on what parts live in the core, and which are candidates for community plugins
  • i.e. would an entity provider working with instances of the json schema live in core, but plugins that map to hugging face, kubeflow, mlflow, etc. live as community plugins, with possible promotion to the core 
  • i.e. or some other core vs. community distribution
• creation of
  • upstream issues if appropriate to track implementation work