Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix MCP tool call logs not visible in UI Logs tab [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#23878•Fetched 2026-04-08 00:54:05
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
madhu19991madhu19991
Participants
madhu19991madhu19991

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.

Root Cause

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.

RAW_BUFFERClick to expand / collapse

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

extent analysis

Fix Plan

To address the issue of MCP tool calls not being visible or filterable in the LiteLLM UI Logs tab, we will implement the following steps:

  • Add a call_type filter to the UI Logs tab
  • Include a call_mcp_tool option in the call_type filter
  • Modify the model name filter to include a blank/empty option

Code Changes

Here are the necessary code changes:

# Add call_type filter to UI Logs tab
filters = [
    # ... existing filters ...
    {
        'name': 'call_type',
        'options': [
            {'value': 'call_mcp_tool', 'label': 'MCP Tool Call'},
            # ... other call types ...
        ]
    }
]

# Modify model name filter to include blank/empty option
model_name_filter = {
    'name': 'model_name',
    'options': [
        {'value': '', 'label': 'None'},
        # ... existing model name options ...
    ]
}

Configuration Changes

No configuration changes are required for this fix.

Temporary Workaround

As a temporary workaround, users can filter MCP tool calls in the spend logs by using the call_type: call_mcp_tool filter.

Verification

To verify that the fix worked, follow these steps:

  1. Open the UI → Logs tab
  2. Select the call_type filter and choose call_mcp_tool
  3. Verify that MCP tool calls are displayed in the logs
  4. Select the model name filter and choose the blank/empty option
  5. Verify that MCP tool calls are displayed in the logs

Extra Tips

To prevent similar issues in the future, it's recommended to:

  • Regularly review and update the UI filters to ensure they align with the available data
  • Implement automated testing to catch filter-related issues before they reach production
  • Consider adding a "debug" or "verbose" mode to the UI to help with troubleshooting and debugging.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#tensor shape#autograd error#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix MCP tool call logs not visible in UI Logs tab [1 participants]