Support Customer-Specific MCP Server URL in Docker MCP Toolkit Catalog

[JoshQlikDesign]

Feature request: Support customer-specific URLs for MCP server entries

Background:
We are a company that offers a hosted MCP server, but the URL is unique and dedicated for each customer. For example, our server entry point pattern is:

https://<customer-namespace>.mycompany.com/mcp

Every customer has their own subdomain and URL, though it is always the same MCP software/server behind the scenes. This is common for SaaS companies offering multi-tenant or dedicated hosting.

Problem:
The current catalog directory and PR workflow only support a single, static URL in server.yaml for a remote MCP server. There is no way to indicate that each customer must register with a unique URL, or to allow UI/UX flows that prompt the user to enter their own instance URL at integration time.

Desired Solution:

• Add support for registering an MCP server pattern or template, e.g. https://CUSTOMER.mycompany.com/mcp
• Allow the catalog (and UIs that consume it) to prompt the end-user for their specific customer subdomain/instance URL during configuration.
• Enable documentation to clarify that the MCP server must be added with a customer-specific URL and provide guidance for onboarding.
• (Optional) Consider additional config entry fields to mark registrations as "multi-tenant, requires custom URL" versus global public endpoints.

Benefits:

• Supports SaaS/multi-tenant MCP providers and customer-dedicated deployments
• Enables more vendors to list their offerings in the catalog
• Expands what kind of MCP servers can be onboarded

Example Use Case:

Customer Acme signs up for our offering and has acme.mycompany.com/mcp as their endpoint, while BigCo uses bigco.mycompany.com/mcp. Each can add their unique MCP endpoint but both use the same underlying MCP server inside Docker MCP Toolkit.

Related:

• Willing to be a design partner if you want feedback/input

Thanks for considering this enhancement! Please let us know if you'd like a contact for a live use case or want to discuss further.