Skip to content

[BUG]: MAX_MEMBERS_PER_TEAM cannot be overriden. #3588

@ja8zyjits

Description

@ja8zyjits

🐞 Bug Summary

MAX_MEMBERS_PER_TEAM once set in the env creates a hard limit for the team membership.
To change this the administrator needs to change the env value and then restart. Even then for existing teams this wont reset the value in the DB.


🧩 Affected Component

Select the area of the project impacted:

  • mcpgateway - API
  • mcpgateway - UI (admin panel)
  • mcpgateway.wrapper - stdio wrapper
  • Federation or Transports
  • CLI, Makefiles, or shell scripts
  • Container setup (Docker/Podman/Compose)
  • Other (explain below)

🔁 Steps to Reproduce

  1. Set MAX_MEMBERS_PER_TEAM as 2
  2. Create a team
  3. Add 2 members
  4. Stop the gateway, update the env MAX_MEMBERS_PER_TEAM to 3 and start the gateway
  5. Add a new member

🤔 Expected Behavior

We need to rethink this issue, should we override the env values programmatically or should we remove this hard limit?


🧠 Environment Info

You can retrieve most of this from the /version endpoint.

Key Value
Version or commit RC-2
Runtime e.g. Python 3.11, Gunicorn
Platform / OS e.g. Ubuntu 22.04, macOS
Container e.g. Docker, Podman, none

Additional Context:

There is an API to override this value

curl -X 'PUT' \
  'http://localhost:8080/teams/<team_id>' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
  "name": "string",
  "description": "string",
  "visibility": "private",
  "max_members": 200
}'

But this is not documented anywhere.

Metadata

Metadata

Assignees

Labels

MUSTP1: Non-negotiable, critical requirements without which the product is non-functional or unsafebugSomething isn't workingpythonPython / backend development (FastAPI)wxowxo integration

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions