6 views
-/https://github.com/berriai/litellm/issues/25866
GitHub · issue

#25866 [Bug]: MCP Access Groups can't be assigned to key not in a team

  • State: open
  • Author: @brandonbiggs
  • Labels: bug, proxy

### Check for existing issues

- [x] 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

```shell

```

### What part of LiteLLM is this about?

Proxy

### What LiteLLM version are you on ?

v.183.3

### Twitter / LinkedIn details

_No response_

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 · 31d18h30m29s ago — entered · #import:https:::github.com:berriai:litellm post #2370
#33401 has greater implementation risk: it crosses provider-specific request translation, model capability detection, backward compatibility, and regression-test coverage. #25866 is more localized to proxy authorization and resource-assignment validation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search