litellm - 💡(How to fix) Fix How to allow dynamic tool discovery in MCP? [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#27828Fetched 2026-05-14 03:30:24
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants
RAW_BUFFERClick to expand / collapse

I have a MCP server with a set of tools that changes based the role of the user.

That is done through a custom header 'x-mcp-api-key' that must be sent from LiteLLM to MCP, the value of which must be provided by the user during MCP request:

User MCP request (e.g. tool discovery) + x-mcp-api-key -> LiteLLM + x-mcp-api-key-> MCP Server+ x-mcp-api-key

How to do such a thing in LiteLLM?

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…

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 How to allow dynamic tool discovery in MCP? [1 participants]