[Bug]: Team Selection implementation not tagging or loading added servers, tools, gateways

[kevalmahajan]

🐞 Bug Summary

Resources(servers, gateways, tools) created after selecting a team are not being tagged with the selected team_id and owner_email, resulting in incorrect or missing associations in the database. Additionally, selecting a team does not load its associated resources in the UI.

---

🧩 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. Navigate to the UI and select any available team from the team selection dropdown/menu.
2. Create a new resource (e.g., an MCP server or virtual server).
3. Inspect the request payload or database entry, observe that team_id and owner_email are missing or blank.
4. Select a different team from the team list.
5. Observe that the UI does not load or display any resources specific to the selected team as they are not tagged to any team.

---

🤔 Expected Behavior

1. Any new resources (e.g., MCP servers, virtual servers, tools, etc.) created while the team is selected should be tagged to that specific team.

2. Upon selecting a team, all existing resources associated with that team should be fetched from the backend and displayed in the UI.

---

🧠 Environment Info

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

Key	Value
Version or commit	e.g. v0.9.0 or main@a1b2c3d
Runtime	e.g. Python 3.11, Gunicorn
Platform / OS	e.g. Ubuntu 22.04, macOS
Container	e.g. Docker, Podman, none

---

🧩 Additional Context (optional)

Add any configuration details, flags, or related issues.