What happened?
When adding an MCP server in the LiteLLM UI, the browser (client-side)s used to fetch the MCP server’s tool list and descriptions. The backend should be making this request.
This breaks in private or internal K8s setups where the MCP server is only reachable from within the cluster.
Users see a misleading error
Backend proxy configuration is valid; the issue is UI-side fetch routing.
Relevant log output
Received non-JSON response (500: ). Check network tab for details.
Are you a ML Ops Team?
No
What LiteLLM version are you on ?
v1.78.5
Twitter / LinkedIn details
No response