Auth Header Fix for MCP Tool Call - #15736
Conversation
|
@1vinodsingh1 is attempting to deploy a commit to the CLERKIEAI Team on Vercel. A member of the Team first needs to authorize it. |
|
|
|
@ishaan-jaff @krrishdholakia |
|
I have signed CLA just now
…On Mon, Oct 20, 2025 at 9:32 AM CLAassistant ***@***.***> wrote:
*CLAassistant* left a comment (BerriAI/litellm#15736)
<#15736 (comment)>
[image: CLA assistant check]
<https://cla-assistant.io/BerriAI/litellm?pullRequest=15736>
Thank you for your submission! We really appreciate it. Like many open
source projects, we ask that you sign our Contributor License Agreement
<https://cla-assistant.io/BerriAI/litellm?pullRequest=15736> before we
can accept your contribution.
You have signed the CLA already but the status is still pending? Let us
recheck <https://cla-assistant.io/check/BerriAI/litellm?pullRequest=15736>
it.
—
Reply to this email directly, view it on GitHub
<#15736 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATWI54YNNRDQARS4O3R5Y5D3YTW73AVCNFSM6AAAAACJV6I4TSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMRSGM2DCMRZHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
…insensitive_servername_matching added
|
@1vinodsingh1 curious, why're you using |
|
@krrishdholakia Using /mcp-rest/tools/call instead of the normal /mcp routes because the auth header extraction fix is specifically for the REST endpoints. UI sends bearer tokens via HTTP headers. |
|
Also, for route /mcp does not have the same issue of missing auth header but I have not tested /mcp route. |
|
UI sends bearer tokens via HTTP headers. So the auth header extraction fix
is specifically for the REST endpoints.
Pls me know if you have more questions
…On Mon, Oct 20, 2025 at 10:48 PM Krish Dholakia ***@***.***> wrote:
*krrishdholakia* left a comment (BerriAI/litellm#15736)
<#15736 (comment)>
@1vinodsingh1 <https://github.com/1vinodsingh1> curious, why're you using
/mcp-rest/tools/call instead of the normal /mcp routes?
—
Reply to this email directly, view it on GitHub
<#15736 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATWI547ZF32DJMCS5ZHO6Y33YWUKFAVCNFSM6AAAAACJV6I4TSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMRUGU3DCMBVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi @1vinodsingh1, I'd like to ask: is this issue — #15957 — caused by the problem you mentioned? |
|
It looks like similar issue of auth header authentication in web search. |
@1vinodsingh1 If you have time, please help take a look at this issue, thank you. |
* fixed the Auth header for MCP Tool Call * Final fix for Auth header * testcase for mcp_auth_header_extraction, insensitive_alias_matching, insensitive_servername_matching added
3 participants
Title
Relevant issues
Pre-Submission checklist
** FIX: Invoke Tool** The LiteLLM REST API endpoint
/mcp-rest/tools/callwas not extracting thex-mcp-authheader from incoming HTTP requests which is fixed now.** FIX: Added case-insensitive matching to handle auth header keys that may not match
# the exact case of server alias/name (e.g., '1litellmagcgateway' vs '1LiteLLMAGCGateway')
Type
Bug Fix
🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test
Changes