MCP Connector: Support Multiple Organizations

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:
• List and access all organizations the user has access to
• Allow org-scoped operations (e.g., org_id parameter)
• Maintain authenticated access across multiple orgs

Why This Works
Other MCP connectors (Google Drive, GitHub, etc.) already handle multi-account scenarios, and the MCP protocol supports this pattern.