Problem
In production environments, deployers often host the WebUI on localhost and use a reverse proxy (such as Nginx or Apache) for load balancing and HTTPS termination. The current implementation in the MCP server generates WebUI links using the host and port directly from the configuration file, which may not be reachable from external clients.
Proposed Solution
Add a configuration option to specify a public/deployment WebUI address that should be used for link generation. This would allow deployers to specify the externally accessible URL (e.g., https://clp.example.com) while maintaining the internal host/port configuration for direct connections.
Context
The WebUI itself uses relative paths when generating links to avoid referencing the configured host and port directly. The MCP server should provide a similar capability for deployments behind reverse proxies.
References
Problem
In production environments, deployers often host the WebUI on
localhostand use a reverse proxy (such as Nginx or Apache) for load balancing and HTTPS termination. The current implementation in the MCP server generates WebUI links using the host and port directly from the configuration file, which may not be reachable from external clients.Proposed Solution
Add a configuration option to specify a public/deployment WebUI address that should be used for link generation. This would allow deployers to specify the externally accessible URL (e.g.,
https://clp.example.com) while maintaining the internal host/port configuration for direct connections.Context
The WebUI itself uses relative paths when generating links to avoid referencing the configured host and port directly. The MCP server should provide a similar capability for deployments behind reverse proxies.
References