Curated Registry for Enterprise

[martinarvaiaccedo]

Pre-submission Checklist

• I have checked that this question would not be more appropriate as an issue in a specific repository
• I have searched existing discussions and documentation for answers

Question Category

• Protocol Specification
• SDK Usage
• Server Implementation
• General Implementation
• Documentation
• Other

Your Question

Hi there!

As an Enterprise, we'd like to create a curated list of MCP servers that we allow using Github's new "Restrict MCP access to registry servers" feature.

When creating a new registry, the only way to store a curated list is through the seed.json, otherwise one has no rights to publish others MCP server. This makes updates to our registry impossible without rebuilding from seed from scratch.

Does anyone have a quick guide on whats the quickest and best way to curate our own list? I am sure I'm missing something obvious.

Thanks in advance!

[martinarvaiaccedo]

Since then I was able to grab a representation of the github server and cherry-pick 2-3 servers to test if it is working with a static json. It does after some tweaks in VSCode Insiders, however this (static json) still feels a bit flaky for an enterpirse-ready solution.

[aarora79]

A take at an enterprise MCP registry: https://github.com/agentic-community/mcp-gateway-registry.

[rdimitrov]

hey, @martinarvaiaccedo 👋 Thanks for reaching out and raising your question. Can you share more about your use case and the expectations that you have from the registry project?

Overall, the goal of the registry project is to:

• Host the code for the public good instance of the Official MCP registry service
• Define the server.json + the OpenAPI specs compliant with the Official MCP registry

That said using the project as a standalone on-premise instance is out of scope (at least for now).

If this is your case there are other projects that potentially try to address that problem, i.e. like the project mentioned above, Toolhive's take on a k8s enterprise MCP registry (Link to the app, stacklok/toolhive#1740), etc.

[martinarvaiaccedo]

Thank you @aarora79 , @rdimitrov for your response! Let me clarify what the intention is. I realize I skipped some important parts. So as an organization, we would like to control the list of MCPs our engineers use. For this, Github released the following feature: https://github.blog/changelog/2025-09-12-internal-mcp-registry-and-allowlist-controls-for-vs-code-insiders/
This says, (and I have tested it with a simple static json representation of a registry) that we can control Copilot clients MCP access with such list. This feature itself is clear, but it doesn't align well with the purpose / methodology of the mcp registry so I sense some mismatch in the air.
The question rephrased would be "how can i create my own registry with just 15 MCP servers so I can control my organization via this Github Feature".

Thanks again for looking into this!

[rdimitrov]

Thanks for clarifying, that makes perfect sense! 🙏

From what I understand you have to create a json file following the version of the upstream format GitHub adopted at that point of time, but I haven't tried it so cannot confirm if that would work 😃 I think we agree this is specific to the GitHub Copilot allowlist feature rather than the official MCP registry itself and it is outside the registry’s scope so it might be best to reach out to the Copilot support team or community for guidance on how to enable this properly.

[martinarvaiaccedo]

Oki, thank you! Just FYI, I have tried and it does work, they are following the registry's spec. It's just then a weird scenario of using registry "not what its for" I guess 🤷 I mean... I am confused honestly on how do I fill up my own registry of other's MCP servers other than seeding or manually editing the json 😁 Thanks anyway!!