Skip to content

docs(mcp): note v1.95.0 as the first release with the complete DCR bridge flow - #659

Open
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1784934827-dcr-bridge-version-note
Open

docs(mcp): note v1.95.0 as the first release with the complete DCR bridge flow#659
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1784934827-dcr-bridge-version-note

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Summary

The "oauth_delegate with the bridge" section documents the employee-bound flow as if any release supports it, which is what prompted BerriAI/litellm#34566. It does not: on v1.93.0 exchange_token_with_server returns the upstream provider token verbatim (build_bridge_token_response has no production caller at that tag, and bridge_token_flow.py does not exist), and the v1.94.0 train adds the token-endpoint mint plus the SSO user subject (BerriAI/litellm#32828, BerriAI/litellm#32946) without the aggregate /mcp session admission that reloads live user and team permissions per call (BerriAI/litellm#33190, first tagged in v1.95.0-dev.2).

Adds a "Version availability" info admonition to that section stating v1.95.0 as the requirement and spelling out what is missing on v1.93.0 and on the v1.94.0 RCs, so readers on require_key_mcp_access_defined: true know why an employee gets no explicit server/tool permissions there.

Validated with npm run build; the remaining warnings are pre-existing on main.

Link to Devin session: https://app.devin.ai/sessions/8d1cc99297754a8887a27e1138e4e24c

@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@vercel

vercel Bot commented Jul 24, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview, Comment Jul 24, 2026 11:22pm

Request Review

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.

0 participants