MCP tool call logs not visible in UI Logs tab

[madhu19991]

Description

MCP tool call logs are not visible or accessible in the LiteLLM UI Logs tab. While they appear in spend logs with call_type: call_mcp_tool, there is no way to filter or navigate to them in the UI.

Expected Behavior

Per the v1.81.6 release notes and UI Logs documentation, MCP tool calls should be visible and filterable in the Logs v2 interface with:

• Tool call payloads (arguments, responses)
• Which MCP server was called
• Collapsible side panels for correlating activities

Actual Behavior

• MCP tool calls do appear in spend logs with call_type: call_mcp_tool
• However in the UI Logs tab, the model name filter does not include a blank/empty option — so MCP calls (which have no model name) cannot be filtered to at all
• There is no call_type filter in the UI
• MCP activity only surfaces as an aggregate line item (MCP: list_tools) in /spend/logs daily summaries

Steps to Reproduce

1. Configure an MCP server (HTTP transport, OAuth2 or API key auth)
2. Make a tool call through the MCP server
3. Open UI → Logs tab
4. Try to filter to MCP calls — not possible, blank model name is not an available filter option

Environment

• LiteLLM version: v1.81.14
• Deployment: Kubernetes (GKE)
• MCP transport: HTTP (Streamable HTTP)

Requested Improvement

• Add call_type as a filterable field in the Logs UI with a dedicated call_mcp_tool option
• Or add a blank/empty model name as a selectable filter option
• Or provide a dedicated MCP activity log view

This would enable:

• Debugging tool call failures
• Auditing which tools were called and with what arguments
• Per-request cost attribution for MCP tool usage

[auggie246]

I have submitted a PR to fix this in #30122