Feature Request: Remote Server URL Interpolation with Dynamic Host Parameter

[ThePlenkov]

Feature Request: Remote Server URL Interpolation in Catalog

Problem

Current MCP Registry remote server configuration requires hardcoded remote URLs. Users must create a separate catalog entry for each MCP instance (e.g., staging, production, custom, customer-specific).

This approach cannot easily support dynamic runtime selection or interpolation of the HTTP endpoint, and forces repetition in catalog entries.

Requested Solution

Allow pure URL interpolation in the catalog, leaving host (and potentially other variables) entirely up to the user at runtime.

For example, permit:

remote:
  transport_type: streamable-http
  url: "https://{{host}}/.api/mcp"

• No predefined values, no catalog-time restrictions; interpolation only
• Catalog encodes URL logic (path/scheme/form), but user instance (host/port) is injected by CLI/env/config
• CLI, environment variable, or task parameter fills in host value when running, importing, or enabling the server
• Optionally support additional interpolation variables for more flexible endpoint composition
• No full duplication required for multiple MCP instances; catalog remains DRY

Impact

• Enables multiple MCP/server instances through a single catalog entry
• Allows flexible endpoint composition for more complex setups
• Reduces catalog repetition, improves maintainability

Example

remote:
  url: "https://{{host}}/.api/mcp"

Or similar convention for runtime interpolation (could use ${host} syntax, but {{host}} is more explicit for template engines)

References

• Original feature request
• Common SaaS patterns (e.g., Sourcegraph MCP, customer-tenancy)

---

Please consider adding pure-string interpolation for remote server URLs in MCP Registry catalogs!

[ThePlenkov]

the use case comes from the idea to create sourcegraph mcp with configurable url. Thanks!