18 views
-/https://github.com/berriai/litellm/issues/19735
GitHub · issue

#19735 [Feature]: Include metadata for list_mcp_tools in StandardLoggingPayload

  • State: open
  • Author: @jeromeroussin
  • Labels: enhancement, proxy

### Check for existing issues

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

### The Feature

list_mcp_tools calls generate a custom callback call since https://github.com/BerriAI/litellm/commit/872e5b98977eac7eea95be6fd6069e751709960a

But the payload provided does not contain much, particularly it lacks mcp_server_name, ie where the list_mcp_tools call was targeted to.

### Motivation, pitch

Better observability of mcp protocol

### 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

https://www.linkedin.com/in/jeromeroussin/

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h55m46s ago — entered · #import:https:::github.com:berriai:litellm post #1943
Requires tracing specialized model-call accounting through usage aggregation, persistence, and dashboard presentation, with validation across reporting paths; the other is a localized observability-payload change with comparatively limited surface area.
#0 of 0 · 31d18h18m39s ago — current · #import:https:::github.com:berriai:litellm post #2542
The left task spans a new user-facing CLI workflow, multiple diagnostic integrations, output design, compatibility handling, and broad testing. The right task is a narrower observability-schema and propagation change within an existing request path, with focused tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search