litellm - 💡(How to fix) Fix [Bug]: MCP Access Groups can't be assigned to key not in a team [1 comments, 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#25866Fetched 2026-04-17 08:28:30
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×2commented ×1

Error Message

In litellm 1.82.3 I was able to assign an mcp access group to a key. In litellm 1.83.3, no matter what I change, I continually get an error that states the key must be assigned a team.

RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

In litellm 1.82.3 I was able to assign an mcp access group to a key. In litellm 1.83.3, no matter what I change, I continually get an error that states the key must be assigned a team.

I read the comments in the code that this should work, but it doesn't - https://github.com/BerriAI/litellm/blob/26937a21461f6428f1029e2c39f33a785f8f3f19/litellm/proxy/management_helpers/object_permission_utils.py#L346

Steps to Reproduce

  1. Create key and don't assign a team
  2. Create mcp server
  3. create mcp server access group
  4. attempt to assign key to mcp server access group

Relevant log output

What part of LiteLLM is this about?

Proxy

What LiteLLM version are you on ?

v.183.3

Twitter / LinkedIn details

No response

extent analysis

TL;DR

The issue may be resolved by re-examining the code changes between litellm 1.82.3 and 1.83.3, specifically focusing on the object permission utilities.

Guidance

  • Review the object_permission_utils.py file, particularly the lines around the mentioned comment (#L346), to understand the expected behavior and potential changes that could cause the error.
  • Verify that the assign key to mcp server access group step is correctly implemented and that the key is properly created without a team assigned, as per the steps to reproduce.
  • Check for any other code changes or updates in the management_helpers module that could be affecting the key assignment process.
  • Consider testing the key assignment process with different scenarios, such as assigning a team to the key before attempting to assign it to an mcp server access group, to isolate the issue.

Example

No code snippet is provided as the issue lacks specific details about the code changes.

Notes

The issue may be related to a change in the permission logic or validation between litellm 1.82.3 and 1.83.3, but without more information, it's difficult to provide a definitive solution.

Recommendation

Apply workaround: Attempt to assign a team to the key before assigning it to an mcp server access group, and then try to assign the key to the mcp server access group again, to see if this resolves the issue. This is because the error message specifically states that the key must be assigned a team.

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 [Bug]: MCP Access Groups can't be assigned to key not in a team [1 comments, 1 participants]