8 views
-/https://github.com/berriai/litellm/issues/32235
GitHub · issue

#32235 [Feature]: Add per-MCP-server usage count metric (Prometheus)

  • State: open
  • Author: @orich4321
  • 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

Add a metric (with an MCP server name label) that tracks how many times each MCP server has been called, so this count can be queried per server via PromQL.

### Motivation, pitch

I'm building a dashboard to show usage of each MCP server. Right now I can't measure how many times each MCP server has been used, since the Prometheus metrics don't expose a per-MCP-server usage count. Adding this would let me build a dashboard showing usage counts for each MCP server.

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

www.linkedin.com/in/ori-cohen-5124b8163

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d18h15m34s ago — entered · #import:https:::github.com:berriai:litellm post #2595
The left task spans instrumentation, metric design, label/cardinality considerations, integration with the proxy’s MCP execution path, and observability tests. The right task is more localized to configuration propagation or lookup consistency, with a narrower regression-test surface and lower architectural risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search