Allow configuration of MCP registries for dynamic connector support
🚀 Describe the new functionality needed
This effort will introduce MCP registries as registered_resources in the run.yaml alongside connectors
apis: ...
providers: ..
storage: ..
registered_resources:
models: ..
...
connectors:
- connector_id: connector_github
url: https://api.github.com/mcp
- connector_id: connector_gitlab
url: https://gitlab.com/mcp
- connector_id: connector_slack
url: https://slack.com/mcp
connector_registries: # EDIT
- name: registry_internal
id: internal
url: https://registry.internal.dev/
- name: registry_public
id: public
url: https://registry.public.dev/
...
Each dynamically discovered server produces a unique connector_id in the form mcp::<registry_id>::<server_name> This convention ensures uniqueness across registries and provides users with a stable, self-describing identifier. Administrators must ensure all registry_id values are unique within the run.yaml.
💡 Why is this needed? What if we don't build it?
Building on #4186 this issue extends connector configuration options to also include MCP registries. The server can query configured MCP registries to see all the servers that are made available through them and generate dynamic connectors that will be exposed via the conenctors API described in #4235
Other thoughts
No response
if we are calling them connectors, should this be called "connectors_registries" to be consistent, in the future we something other than MCP pops up we can add a "type"?
if we are calling them connectors, should this be called "connectors_registries" to be consistent, in the future we something other than MCP pops up we can add a "type"?
sure, updated the issue description
This issue has been automatically marked as stale because it has not had activity within 60 days. It will be automatically closed if no further activity occurs within 30 days.
closing based on reduced/non existent community demand may be reopened if that changes