### Check for existing issues

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

### What happened?

We're seeing an inconsistency between the LiteLLM API and the UI regarding MCP visibility. The Virtual Key has access to the expected MCP Access Groups, and the MCP tools are accessible through the API. However, the LiteLLM UI does not display any MCPs for the same Virtual Key.

Expected behavior

When using the UI with this Virtual Key, the user should see the MCP servers/tools that are accessible through the assigned Access Groups.

The UI should reflect the same permissions enforced by the API.

Actual behavior

The API works correctly:

GET /v1/mcp/tools returns the expected MCP tools.

Calls to the MCP tools succeed.

However, the UI shows no MCP servers/tools for the same Virtual Key.

This appears to be a UI issue rather than an authorization issue, since the API correctly enforces the Access Group permissions.

Is the UI expected to display MCPs available through the Virtual Key's Access Groups, or is this a regression in the MCP Hub UI

### Steps to Reproduce

Create an MCP Server.

Assign it to an Access Group.

Create a Virtual Key. …