<![CDATA[Proget as MCP Server Registry/Gateway]]>We're beginning to explore broader MCP adoption within our organization and have started looking at products to serve as a MCP server Registry and Gateway.

Our ideal solution would allow us to:

  • Register MCP servers centrally.
  • Maintain an approved catalog of MCP servers that users can discover.
  • Control who can access specific MCP servers.
  • Apply enterprise governance and auditing around MCP consumption.
  • Give security and platform teams confidence that only vetted MCP servers are available.
  • Audit Usage and Adoption -- how many users/teams are using permitted MCP Servers

I'd be interested to hear whether others in the community have similar requirements or if this is something already being considered for the roadmap.

]]>https://forums.inedo.com/topic/5815/proget-as-mcp-server-registry-gatewayRSS for NodeThu, 13 Aug 2026 16:20:28 GMTTue, 11 Aug 2026 15:19:29 GMT60<![CDATA[Reply to Proget as MCP Server Registry/Gateway on Tue, 11 Aug 2026 17:19:52 GMT]]>Hi @dan.brown_0128 ,

Here's our current position on MCP Registries:

From a quick read of the documentation, it looks like an "MCP Registry" is mostly just a JSON document that lists "MCP Servers". There don't seem to be "Packages" (i.e. an archive file with a manifest file) nor a "Central Repository" (i.e. a canonical location where OSS Models are stored), which means it's not a great fit for ProGet.

Here's the current discussion on the topic: Request to support MCP registry; I'd encourage you to add your thoughts to that!

-- Dean

]]>https://forums.inedo.com/post/19951https://forums.inedo.com/post/19951Tue, 11 Aug 2026 17:19:52 GMT