Skip to content

docs(release-notes): explain the delegate_auth_to_upstream MCP breaking change in v1.103.0 - #2200

Merged
shivamrawat1 merged 1 commit into
mainfrom
litellm_docs_mcp_delegate_breaking_change
Oct 9, 2026
Merged

shivamrawat1 merged 1 commit into
mainfrom
litellm_docs_mcp_delegate_breaking_change

Conversation

@shivamrawat1

Copy link
Copy Markdown
Contributor

The v1.103.0 breaking change entry for PR #40923 said delegated MCP integrations get 401 until they "admit", which didn't tell readers what they'd see or what to change. A customer upgrading from v1.101 to v1.104 hit this on every external and internal MCP server and read it as a regression

This rewrites the entry to say what changed and why (bearer-only requests to delegate_auth_to_upstream servers were anonymous and missing from spend logs), the two 401 messages users actually see (No matching public key found and Audience doesn't match), and the fix: send the LiteLLM credential in x-litellm-api-key and keep the upstream token in Authorization, or migrate to oauth_delegate. It also notes true_passthrough as the opt-in for servers that should stay anonymous

🤖 Generated with Claude Code

…ng change in v1.103.0

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
litellm Ready Ready Preview Oct 9, 2026 3:07am UTC

Request Review

@shivamrawat1
shivamrawat1 merged commit 4565da8 into main Oct 9, 2026
5 checks passed
@shivamrawat1
shivamrawat1 deleted the litellm_docs_mcp_delegate_breaking_change branch October 9, 2026 04:02

This branch was successfully deployed

1 active deployment
Preview — 1a5caacb Deployed Oct 9, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant