6 views
-/https://github.com/berriai/litellm/issues/30468
GitHub · issue

#30468 [Feature]: Include static/extra headers in MCP usage examples and copy snippets

  • State: open
  • Author: @RytisStreimikis
  • Labels: enhancement, ui-dashboard

### Check for existing issues

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

### The Feature

When rendering the MCP usage example and the copy-to-clipboard snippet in ui/litellm-dashboard/src/components/public_model_hub.tsx, include any configured static_headers/extra_headers (e.g. X-API-Key) from the selectedMcpServer object so the generated client configuration includes the required headers.

### Motivation, pitch

Currently, the example snippets omit required headers, causing copied examples to fail with authentication errors in common deployments. Including these headers makes the examples runnable and reduces confusion/support burden for users configuring MCP servers that require custom headers.

### What part of LiteLLM is this about?

UI Dashboard

### LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

### Twitter / LinkedIn details

@RytisStreimikis

GitHub resolver

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

Refresh page
vote history (9 events)
#0 of 0 · 31d19h26m49s ago — entered · #import:https:::github.com:berriai:litellm post #1633
#34906 requires deeper proxy-side MCP protocol routing, URI ownership resolution, and multi-server regression testing; #30468 is a localized dashboard rendering and snippet-generation change.
29998 requires coordinated backend normalization, usage-model changes, and streaming aggregation compatibility across providers and tests; 30468 is comparatively localized dashboard rendering and snippet-generation work.
The right item is harder because it spans shared UI rendering and copy-generation paths, with added header serialization and sensitive-data handling concerns. The left has a focused, already-implemented change with regression coverage.
30365 is harder because it spans proxy request flow, authentication passthrough, rate-limit handling, retries or fallback behavior, and tool-execution failure semantics. 30468 is a localized dashboard rendering change with comparatively limited integration and testing scope.
The left issue is harder because it involves diagnosing deployment-specific database tooling, container/engine compatibility, migration behavior, and potentially dependency or build changes. The right issue is a localized dashboard rendering and clipboard-generation adjustment with comparatively limited integration risk.
The left requires backend data-access redesign, memory-safe pagination or projection, compatibility validation, and load/regression testing across session reconstruction paths. The right is a localized dashboard rendering change with comparatively limited integration and testing scope.
The harder item requires coordinated cross-cutting frontend error handling, authentication-state recovery, routing, and regression testing across multiple request paths. The easier item is a localized UI-generation change with a smaller surface area and simpler verification.
The dashboard work requires tracing configuration data through rendering and clipboard-generation paths, handling UI state and validation, and adding coverage; the endpoint fix is comparatively localized to routing behavior with focused regression testing.
#0 of 0 · 31d18h15m7s ago — current · #import:https:::github.com:berriai:litellm post #2808
The left issue requires tracing and correcting shared asynchronous routing, retry propagation, exception metadata, cooldown selection, and regression coverage across multiple provider-facing paths. The right issue is a localized dashboard rendering change with comparatively limited integration risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search