Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Request to support MCP registry
-
Hi,
With GitHub Copilot and MCP server we can use an url to white list MCP server.
It could me nice to have Proget as an MCP registry for this purpose.https://docs.github.com/en/copilot/how-tos/administer-copilot/configure-mcp-server-access
https://github.com/modelcontextprotocol/registry
Regards,
Frédéric
-
Hi @fhusson_1634 ,
From a quick read of the documentation, it looks like an "MCP Registry" is basically a list of "MCP Servers", which is basically a JSON document that describes.... an API or something?
What I'm not seeing are "Packages" (i.e. an archive file with a manifest file) nor a "Central Repository" (i.e. a canonical location where OSS Models are stored). If that's the case, I'll do a "hard pass" on this for the forseeable future -- there's not much value ProGet could add here and we'd have to add a completely separate, non-package subsystem like Assets or Docker.
Let me know if I misread the specs
Thanks,
Alex
-
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
