Add read-only and project scoping options to the official Supabase Claude connector

Problem


When connecting Supabase to Claude via the official connector, there's no way to restrict access. Once authorized, Claude gets full write access to every project in the organization.

The Supabase MCP server itself supports read-only mode and project scoping — they're just not exposed in the connector flow. So the official, recommended path is also the least safe one.

What I'd like

During the connector setup in Claude, let me:
• Pick which project to scope access to
• Toggle read-only mode on

These are already first-class features of the MCP server. They just need to surface in the connector UI.

Why it matters


Supabase's own best practices recommend read-only and project scoping by default. Without these controls in the connector, users either accept full write access on their whole org, or skip the official integration entirely and wire things up manually.