Adhoc v1.88.0 backport: MCP OAuth/Tools fixes + allowlist update-500 fix (#29411) + card grid

[tin-berri]

Relevant issues

Adhoc backport branch off the v1.88.0 tag (base release/v1.88.0). It cherry-picks a set of already-merged MCP OAuth and Tools-tab fixes, plus a helm config mount and a slack token-lifetime fix, then adds the two dependencies those fixes turned out to need on this older base and the MCP servers card-grid UI.

What this is

v1.88.0-adhoc branches directly off v1.88.0 and carries these merged PRs as individual squash commits, in merge order:

• fix(helm): Enable Backend Deployment to mount Gateway config.yaml #29605 fix(helm): enable backend deployment to mount Gateway config.yaml
• fix(ui): route MCP playground auth by oauth2 mode instead of token_url #29714 fix(ui): route MCP playground auth by oauth2 mode instead of token_url
• fix(mcp): persist Tools-tab MCP OAuth token to DB #29809 fix(ui): persist Tools-tab MCP OAuth token to DB
• fix(ui): stop MCP playground tool calls from sending twice #29821 fix(ui): stop MCP playground tool calls from sending twice
• fix(mcp): let non-creator users OAuth into OBO-mode MCP servers from the Tools page #29867 fix(mcp): let non-creator users OAuth into OBO-mode MCP servers from the Tools page
• fix(mcp): mirror upstream token lifetime instead of forcing a 1h OBO expiry #29951 expires_in default uses actual slack return details
• fix(mcp): load MCP tool configuration tools via the OBO/passthrough-aware GET path #29960 fix(mcp): load MCP tool configuration tools via the OBO/passthrough-aware GET path
• fix(ui/mcp): reset OAuth state on create-server modal close so a prior server's token no longer leaks into the next add-server session #30000 fix(ui/mcp): reset OAuth state on create-server modal close so a prior server's token no longer leaks into the next add-server session
• fix(mcp): allow team access-group grants in OAuth authorize/token access check #30041 fix(mcp): allow team access-group grants in OAuth authorize/token access check

A test(mcp): drop backported tests for features absent from v1.88.0 commit removes tests that git's conflict resolution pulled in from intermediate commits that are not part of this set (per-user env-var rotation from #28917, the MCP upstream-auth exception module from #28356). Those tests exercise code that does not exist on v1.88.0, so they cannot pass here; the genuine regression tests added by #29809 and #29960 stay and pass.

Added dependencies and UI

Two things were added on top because the cherry-picks above depend on them when applied to a base this old:

• fix(mcp): clear allowed_tools and tool overrides on MCP server edit #29411 fix(mcp): clear allowed_tools and tool overrides on MCP server edit. fix(mcp): load MCP tool configuration tools via the OBO/passthrough-aware GET path #29960 was built on top of fix(mcp): clear allowed_tools and tool overrides on MCP server edit #29411, so without it the tool-allowlist save path reverts to the pre-fix(mcp): clear allowed_tools and tool overrides on MCP server edit #29411 behavior where the dashboard sends allowed_tools: null and the backend passes that straight into the required Prisma String[] column, which surfaces as "Failed to update MCP Server: internal server error". fix(mcp): clear allowed_tools and tool overrides on MCP server edit #29411 sends the array (and the tool_allowlist_enforced flag) and coerces legacy null payloads before Prisma, which fixes the update path.
• A frontend-only MCP servers card-grid list (MCPServerCard plus search and sort). The card layout shipped to staging fused with the per-server env-vars feature; this keeps only the frontend card files and strips the env-vars wiring out of mcp_servers.tsx, so the grid renders standalone with no networking, backend, or DB-migration dependency. The only thing it does not carry is the "N user fields missing" footer, which is the part that genuinely needs the env-vars backend.

A small chore: gitignore ui/litellm-dashboard/out commit stops the generated Next.js build output from being committed.

Conflict handling

Several picks conflicted because these PRs were built on top of intermediate commits between v1.88.0 and staging that are not in this set. Each was resolved to the PR's own intent and verified: #29714 was a prettier-only divergence (#29622 is not in the set), so its mcp_tools.tsx is byte-identical to the PR and the isOAuth to isPassthrough switch is intact; #29809 keeps the resolve_valid_user_oauth_token refactor; #29867 keeps only its genuine TOOLS_OAUTH_UI_STATE_KEY import; #29960 keeps the full apply_tool_filters / include_disabled_tools behavior; and #29411 was merged so that both its allowlist logic and #29960's external-tools logic coexist.

Pre-Submission checklist

• I have added meaningful tests
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

CI (LiteLLM team)

• Branch creation CI run
  Link:
• CI run for the last commit
  Link:
• Merge / cherry-pick CI run
  Links:

Screenshots / Proof of Fix

Each backported commit corresponds one-to-one with an already-reviewed-and-merged PR; the linked PRs carry their own proof of fix. Fidelity of the backport was checked by comparing every original merge commit's changed-line set against its cherry-pick. Tests on this branch: the full MCP backend test directory passes, all MCP dashboard tests pass (including the new "enforces the allowlist when the user explicitly deselects every tool" test that covers the update-500 fix and the card-grid render), and tsc reports no new errors in any touched file.

Type

🐛 Bug Fix

Changes

Backport plus the dependencies the backport needs on v1.88.0, and a frontend-only card-grid for the MCP servers list.

[greptile-apps]

Too many files changed for review. (383 files found, 100 file limit)