Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix [Bug]: mcp does not list tools in logs [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#26487•Fetched 2026-04-26 05:06:40
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
mubashir1osmanimubashir1osmani
Participants
mubashir1osmanimubashir1osmani
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

i see this log for mcp list tools but its not helpful and does not show me what tools were used / listed

<img width="1079" height="795" alt="Image" src="https://github.com/user-attachments/assets/21415a9b-6f5c-4b4f-b410-33019db2bec4" />

Steps to Reproduce

  1. call an mcp tool
  2. check litellm UI logs

Relevant log output

What part of LiteLLM is this about?

UI Dashboard

What LiteLLM version are you on ?

v1.83.13

Twitter / LinkedIn details

No response

extent analysis

TL;DR

The issue may be resolved by checking the LiteLLM UI logs more thoroughly or using a different log level to get more detailed information about the tools used.

Guidance

  • Check the LiteLLM UI logs for any errors or warnings that may indicate why the tools are not being listed.
  • Try increasing the log level to debug or verbose to get more detailed information about the tools being used.
  • Verify that the mcp tool is being called correctly and that the logs are being generated as expected.
  • Review the LiteLLM documentation to see if there are any specific logging configurations or settings that need to be enabled to get the desired log output.

Notes

The issue lacks specific log output, which makes it difficult to provide a more detailed solution. Additionally, the version of LiteLLM being used is v1.83.13, but it is unclear if this is the latest version or if there are any known issues with logging in this version.

Recommendation

Apply workaround: Try increasing the log level to debug or verbose to get more detailed information about the tools being used, as this may provide more insight into the issue.

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…
#retrieval issue#search optimization#API routing#API middleware#SSR setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING