Description
The registry currently auto-registers the airegistry-tools (mcpgw) demo server on every startup via initialize_demo_servers() in the FastAPI lifespan. This is a nice default for getting started, but in production deployments where we manage our own server registrations, it would be great to have a way to opt out.
Use Case
We run the registry in a managed environment where all MCP server registrations are controlled through a GitOps pipeline. Having airegistry-tools appear automatically is confusing for our users since it's not something we've registered or support — they see it in the server list and wonder where it came from.
Suggestion
An environment variable like DISABLE_DEMO_SERVERS=true (defaulting to false to preserve current behavior) that skips the initialize_demo_servers() call:
# In registry/main.py lifespan
if not settings.disable_demo_servers:
from registry.services.demo_servers_init import initialize_demo_servers
await initialize_demo_servers()This keeps the current experience for new users while giving production deployments a clean opt-out.
Environment
Description
The registry currently auto-registers the
airegistry-tools(mcpgw) demo server on every startup viainitialize_demo_servers()in the FastAPI lifespan. This is a nice default for getting started, but in production deployments where we manage our own server registrations, it would be great to have a way to opt out.Use Case
We run the registry in a managed environment where all MCP server registrations are controlled through a GitOps pipeline. Having
airegistry-toolsappear automatically is confusing for our users since it's not something we've registered or support — they see it in the server list and wonder where it came from.Suggestion
An environment variable like
DISABLE_DEMO_SERVERS=true(defaulting tofalseto preserve current behavior) that skips theinitialize_demo_servers()call:This keeps the current experience for new users while giving production deployments a clean opt-out.
Environment