As explored, MCP Registry has a set of API that can be used to automate the publication of information on a MCP Server (metadata, endpoints, etc...) to a central registry.
At some point, it could make sense for an organization to configure the access to a target MCP Registry (connection URL, credentials) and the publication policy (when publishing on dev, when publishing on qa or on prod, when having new gateways that registered with specif labels, etc...). That way, each update they push to Reshapr control plane could result in an update in the target registry.
One important point, though, is that the registry access pattern (REST API Call from the control plane that holds the metadata) is not compatible with the Hybrid deployment, where customers deploy a private MCP Registry (this one cannot be reached from the internet).
2 possible solutions to this problem:
Switch from Hybrid deployment mode to full on-premises
Or, have a specific component (a registry proxy) that operates as a gateway by registering to the control plane using gRPC and then receive streaming information. This proxy would then be in charge of syncing the changes and calling the local private MCP Regsitry using the secured local access.
As explored, MCP Registry has a set of API that can be used to automate the publication of information on a MCP Server (metadata, endpoints, etc...) to a central registry.
At some point, it could make sense for an organization to configure the access to a target MCP Registry (connection URL, credentials) and the publication policy (when publishing on dev, when publishing on qa or on prod, when having new gateways that registered with specif labels, etc...). That way, each update they push to Reshapr control plane could result in an update in the target registry.
One important point, though, is that the registry access pattern (REST API Call from the control plane that holds the metadata) is not compatible with the Hybrid deployment, where customers deploy a private MCP Registry (this one cannot be reached from the internet).
2 possible solutions to this problem:
Switch from Hybrid deployment mode to full on-premises
Or, have a specific component (a registry proxy) that operates as a gateway by registering to the control plane using gRPC and then receive streaming information. This proxy would then be in charge of syncing the changes and calling the local private MCP Regsitry using the secured local access.