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

#28642 GET /v1/mcp/server returns delegate_auth_to_upstream: false when database row is true

  • State: open
  • Author: @tanmaypandey7

## Describe the bug

When an MCP server is created or updated with `delegate_auth_to_upstream: true`, the value persists in PostgreSQL, but `GET /v1/mcp/server` consistently returns `delegate_auth_to_upstream: false`.

This makes the Admin UI toggle appear off after save/reload, and may cause subsequent updates to write `false` back to the database because the UI re-syncs from the GET response.

## To Reproduce

1. Run LiteLLM proxy with `STORE_MODEL_IN_DB=True` and a connected Postgres database (migration `20260513120000_add_delegate_auth_to_upstream_to_mcp_servers` applied). 2. Create or update an OAuth2 MCP server with `delegate_auth_to_upstream: true` via `POST /v1/mcp/server` or `PUT /v1/mcp/server`, or via the Admin UI. 3. Confirm the value in the database:

```sql SELECT server_name, delegate_auth_to_upstream FROM "LiteLLM_MCPServerTable"; -- delegate_auth_to_upstream = true ```

4. Fetch the server via the management API:

```bash curl -s http://localhost:4000/v1/mcp/server \ -H "Authorization: Bearer <proxy-admin-key>" ```

5. Observe that the same server returns `"delegate_auth_to_upstream": false`.

## Expected behavior

`GET /v1/mcp/server` should return the same `del…

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d19h26m36s ago — entered · #import:https:::github.com:berriai:litellm post #1749
Issue 34555 is harder because it requires coordinating invitation-link construction, token/onboarding flow compatibility, configuration handling, and regression coverage across the legacy email path. Issue 28642 is comparatively localized to API response mapping or serialization for a single persisted field.
Issue 30448 requires substantial new architecture, algorithm design, configuration surfaces, runtime integration, persistence of optimization state, cost/latency evaluation, and broad testing. Issue 28642 is comparatively localized to tracing a persisted field through the API response and correcting its mapping or serialization, with focused regression coverage.
#0 of 0 · 31d19h18m23s ago — current · #import:https:::github.com:berriai:litellm post #1873
28642 requires tracing persistence, ORM/model serialization, API response schemas, and regression coverage across proxy and UI flows, with compatibility risk. 33405 is primarily a constrained dependency and lockfile update with focused validation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search