### Check for existing issues

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

### The Feature

When adding new MCP’s if the connection fails the underlying cause isn’t displayed and I need to go looking at logs. Are there any plans to improve ease of troubleshooting MCP connection issues?

<img width="1092" height="141" alt="Image" src="https://github.com/user-attachments/assets/05d4934a-269c-40d0-9539-3e179396c881" />

### Motivation, pitch

Troubleshooting MCP connection errors require spelunking the proxy logs which is time consuming and accessing the logs may not be readily accessible for all users.

### What part of LiteLLM is this about?

Proxy

### LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

### Twitter / LinkedIn details

_No response_