16 views
-/https://github.com/berriai/litellm/issues/23869
GitHub · issue

#23869 [Bug]: issue while adding Custom MCP server

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

While trying to add new Custom MCP Server in UI got the error message: Error creating MCP Server: {"detail":{"error":"Error creating mcp server: Could not find field at `createOneLiteLLM_MCPServerTable.data.approval_status`"}}

### Steps to Reproduce

1. spin up in eks via helm chart, image tag - main-v1.82.3-stable 2. Open UI -> MCP Servers -> Add New MCP Server - > Custom Server 3. filled in all the fields even saw - Connection Status Connection successful 4. But when click on the button "Add MCP Server" got the error message: Error Error creating MCP Server: {"detail":{"error":"Error creating mcp server: Could not find field at `createOneLiteLLM_MCPServerTable.data.approval_status`"}}

### Relevant log output

```shell 15:51:50 - LiteLLM Proxy:ERROR: mcp_management_endpoints.py:1259 - Error creating mcp server: Could not find field at `createOneLiteLLM_MCPServerTable.data.approval_status` Traceback (most recent call last): File "/usr/lib/python3.13/site-packages/litellm/proxy/management_endpoints/mcp_management_endpoints.py", line 1249, i…

Open on GitHub

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d19h12m20s ago — entered · #import:https:::github.com:berriai:litellm post #1766
-/https://github.com/berriai/litellm/issues/23869⭐4:1-/https://github.com/berriai/litellm/issues/26170
The left issue is harder because it likely requires coordinating dashboard behavior, backend mutations, schema compatibility, and deployment or migration handling. The right issue is comparatively localized, with a small set of consistent precedence corrections and focused regression tests.
#0 of 0 · 31d18h57m42s ago · #import:https:::github.com:berriai:litellm post #2002
-/https://github.com/berriai/litellm/issues/23869⭐10:1-/https://github.com/berriai/litellm/issues/32594
The right issue requires tracing a dashboard-to-backend failure, reconciling API schema and database migration compatibility, and validating deployment-version behavior. The left issue is a narrowly scoped catalog/configuration update with limited implementation and testing risk.
#0 of 0 · 31d18h51m20s ago · #import:https:::github.com:berriai:litellm post #2112
-/https://github.com/berriai/litellm/issues/341023:1-/https://github.com/berriai/litellm/issues/23869⭐
Issue 34102 appears broader and less narrowly scoped, likely requiring more investigation and potentially cross-component changes. Issue 23869 is comparatively localized to aligning the MCP creation path with the database schema and deployment migrations.
#0 of 0 · 31d18h35m59s ago — current · #import:https:::github.com:berriai:litellm post #2365
-/https://github.com/berriai/litellm/issues/23869⭐3:2-/https://github.com/berriai/litellm/issues/35428
The right issue is harder because it likely requires coordinating dashboard behavior, proxy management logic, and database schema or migration compatibility, with deployment-version risks. The left issue is more narrowly contained to Azure URL construction and targeted provider tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search