Problem The Supabase MCP connector only allows access to one organization at a time. Users managing projects across multiple organizations (different clients, prod/staging splits, team orgs) can't efficiently manage all projects without manual switching.
Use Case I have separate Supabase organizations for different clients and environments. Currently, I can only access one org per connection, which breaks automation workflows.
Solution Add multi-organization support to the MCP connector:
org_id parameter)Why This Works Other MCP connectors (Google Drive, GitHub, etc.) already handle multi-account scenarios, and the MCP protocol supports this pattern.
Dev-Salem requests multi-organization support for the Supabase MCP connector to manage projects across different clients and environments efficiently. The current limitation to a single organization per connection disrupts automation workflows. The user suggests enhancements like listing all accessible organizations and allowing org-scoped operations.