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

#28527 [Bug]: BYOK for non-OpenAPI spec MCP missing in UI

  • State: open
  • Author: @ry-animal
  • 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?

1. **Create form:** Show BYOK block when `transportType` is `http`, `sse`, or `openapi` (exclude `stdio`). 2. **Edit form:** Add `is_byok`, `byok_description`, `byok_api_key_help_url` to `mcp_server_edit.tsx` for existing servers (read-only hint if toggling off after users have credentials). 3. **Docs:** Clarify BYOK applies to OpenAPI-generated MCP **and** native HTTP MCP servers. Optional: add `GET /v1/mcp/server/{server_id}/user-credential/status` symmetric to `oauth-user-credential/status` for BYOK (today only `has_user_credential` on list endpoint). --- ## Workaround (today) Register via API: ```bash curl -X POST "$LITELLM_BASE/v1/mcp/server" \ -H "Authorization: Bearer $ADMIN_KEY" \ -H "Content-Type: application/json" \ -d '{ "server_name": "my_mcp_server", "url": "https://my-mcp.example.com/mcp", "transport": "http", "auth_type": "bearer_token", "is_byok": true, "allow_all_keys": true, "byok_description": ["Describe access for users"], "byok_api_key_help_url": "https://docs.example.com/api-keys" }'…

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d19h5m18s ago — entered · #import:https:::github.com:berriai:litellm post #1988
Core request execution semantics must be designed consistently across synchronous and asynchronous paths, with configuration, retry timing, jitter, backward compatibility, and broad regression testing. The other change is primarily localized dashboard form work plus documentation and an optional small API addition.
#0 of 0 · 31d18h27m35s ago — current · #import:https:::github.com:berriai:litellm post #2596
The left issue is harder because it requires diagnosing and safely changing concurrent database transaction behavior, with difficult reproduction and regression risk across distributed proxy workloads. The right issue is comparatively localized to dashboard form handling and documentation, with only a small optional API addition.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search