9 views
-/https://github.com/berriai/litellm/issues/31222
GitHub · issue

#31222 MCP per-user OAuth credential management UI removed with /chat route

  • State: open
  • Author: @katzdave

Flagged as worth tracking after a discussion in Slack.

## What happened

PR #30178 ("refactor(ui): remove unreachable /chat page", commit e5a3083c) deleted the `/chat` route and `src/components/chat`. That directory contained `MCPAppsPanel` and its `MCPCredentialsTab`, which was the only place in the dashboard where a user could view and disconnect/revoke their per-user MCP OAuth credentials. This reads as collateral from removing an unreachable route rather than a deliberate deprecation of credential management; the stated rationale was that the route had no sidebar entry, redirect, or backend reference

## Impact

A user can still connect an OAuth MCP server, since the connect flow in `useUserMcpOAuthFlow` and the proxy backend are intact, but there is no longer any UI to list what they have connected or to revoke a credential. The only remaining path is calling the proxy API by hand, which is not viable for non-engineer users

## The backend still supports this

The endpoints and the frontend networking helpers that backed that UI are all still present, just with no callers:

- `DELETE /v1/mcp/server/{server_id}/oauth-user-credential` - `GET /v1/mcp/server/{server_id}/oauth-use…

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d18h14m54s ago — entered · #import:https:::github.com:berriai:litellm post #2588
The right issue spans several provider-specific request paths and shared configuration semantics, requiring careful consistency checks, regression tests, and validation against differing payload schemas. The left issue is comparatively localized to restoring dashboard interactions around existing backend capabilities.
31149 requires cross-cutting backend routing analysis, provider-specific behavior validation, and regression coverage; 31222 is primarily a contained frontend restoration using existing APIs and components.
#0 of 0 · 31d17h37m59s ago — current · #import:https:::github.com:berriai:litellm post #3231
The right issue is harder because it requires rebuilding and integrating a user-facing management workflow across frontend state, API interactions, navigation, and regression coverage; the left issue is a narrowly scoped protocol-normalization fix.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search