Hi, Yes from my understanding you got it right. It's still very young. It's about storing a json "package" or text. In the json you can have a config for an url for a remote MCP server or a package that you can run on your computer to be a local MCP server (only from official repo for now). Maybe in the futur if this kind of registry can validate private package it could be nice to flag a package already in inedo to make it available in the MCP registry. Exemple : An internal team create an npm package for a MCP server or a docker package In proget I can have a MCP Registry with all kind of MCP server and for our own package we can just check an option on the package in proget to have it in the registry. Regards, Frédéric

Hello; this is the first such request for GCP. These are extensible components, and it's possible we can support it very easily -- but we like to partner with customers, since we have very little knowledge about GCP and like to make sure it works in the field before making it public. The best way to get this rolling would be to submit a feature request, and ideally bring it up with your technical account manager to see if it can get escalated.