8 views
-/https://github.com/berriai/litellm/issues/35583
GitHub · issue

#35583 [Bug]: MCP Servers documentation uses PROXY_BASE_URL instead of LITELLM_UI_API_DOC_BASE_URL

  • State: open
  • Author: @jdomke
  • Labels: bug, ui-dashboard

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

UI AI GATEWAY -> MCP Servers documentation -> shows PROXY_BASE_URL instead of LITELLM_UI_API_DOC_BASE_URL

### Steps to Reproduce

1. set PROXY_BASE_URL 2. set LITELLM_UI_API_DOC_BASE_URL 3. access /ui/mcp-servers/ and 'Connect' tab to see the wrong URL

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

UI Dashboard

### What LiteLLM version are you on ?

v1.94.0

### Twitter / LinkedIn details

_No response_

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d18h10m19s ago — entered · #import:https:::github.com:berriai:litellm post #2784
-/https://github.com/berriai/litellm/issues/35583⭐3:1-/https://github.com/berriai/litellm/issues/33937
The left task likely requires tracing dashboard configuration and rendering behavior, validating environment-variable precedence, and adding regression coverage. The right task is primarily a synchronized metadata update across two price catalogs, with limited code impact.
#0 of 0 · 31d18h3m14s ago · #import:https:::github.com:berriai:litellm post #2910
-/https://github.com/berriai/litellm/issues/275164:1-/https://github.com/berriai/litellm/issues/35583⭐
Credential-routing behavior requires tracing provider resolution across deployment and request contexts plus regression coverage, while the UI configuration fix is likely a localized reference correction.
#0 of 0 · 31d17h44m29s ago — current · #import:https:::github.com:berriai:litellm post #3238
-/https://github.com/berriai/litellm/issues/294065:1-/https://github.com/berriai/litellm/issues/35583⭐
The left requires provider-specific response handling, metadata propagation, compatibility decisions, and validation across routing and observability paths. The right is a localized dashboard documentation/configuration fix with limited scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search