Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix Integration: WhichModel MCP for real-time pricing data in model routing [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#25229•Fetched 2026-04-08 03:02:35
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
simonamsharpsimonamsharp
Participants
simonamsharpsimonamsharp

Code Example

{"mcpServers":{"whichmodel":{"url":"https://whichmodel.dev/mcp"}}}
RAW_BUFFERClick to expand / collapse

Feature proposal

Context: LiteLLM abstracts 100+ LLM providers behind a unified interface. Users routing between models need accurate, up-to-date pricing to make cost-optimal decisions.

Proposal: WhichModel is a free MCP server that tracks pricing and capabilities across 100+ models, refreshed every 4 hours. It could complement LiteLLM's routing by providing real-time pricing data.

Potential integration points:

  1. Use WhichModel pricing data to power LiteLLM's cost-based routing
  2. Add WhichModel as an MCP tool example in LiteLLM docs
  3. Use check_price_changes to keep LiteLLM's internal pricing tables current

MCP Config:

{"mcpServers":{"whichmodel":{"url":"https://whichmodel.dev/mcp"}}}

4 tools:

  • recommend_model — cost-optimized suggestions by task type, complexity, budget
  • compare_models — head-to-head comparison with volume cost projections
  • get_pricing — raw pricing data with filters (model, provider, capabilities, price ceiling)
  • check_price_changes — pricing change tracker since a given date

No API key needed for free tier (1,000 req/mo). MIT licensed.

extent analysis

TL;DR

Integrate WhichModel's MCP server into LiteLLM to utilize its real-time pricing data for cost-based routing decisions.

Guidance

  • Evaluate the feasibility of using WhichModel's get_pricing tool to fetch raw pricing data and update LiteLLM's internal pricing tables.
  • Consider implementing the check_price_changes function to keep LiteLLM's pricing information current, leveraging the 4-hour refresh cycle of WhichModel's data.
  • Review the MCP configuration example provided to ensure correct setup of the WhichModel server within LiteLLM.
  • Assess the potential benefits of incorporating WhichModel as an example in LiteLLM's documentation to enhance user awareness of available MCP tools.

Example

No explicit code example is provided due to the lack of specific implementation details in the issue.

Notes

The integration's success depends on the compatibility of WhichModel's API with LiteLLM's existing infrastructure and the accuracy of the pricing data provided by WhichModel.

Recommendation

Apply workaround: Utilize WhichModel's free tier to integrate its pricing data into LiteLLM, given the absence of any mentioned costs or limitations that would necessitate an upgrade to a paid version.

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#mixed precision#training loop#device allocation#model download

Still need to ship something?

×6

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

Back to top recommendations

TRENDING