#Supabase

Read + run-SQL access to your Supabase projects across multiple organizations.

#Get a token

Generate a Personal Access Token (sbp_…) at https://supabase.com/dashboard/account/tokens.

#Recommended scopes

• Use a Personal Access Token, not the project's anon/service-role key.
• Tokens inherit your account's permissions on every org you belong to.
• Generate a separate token per work context (personal vs. client) so you can rotate independently.

#Add it to the vault

bash
mcpvault add supabase

Example session:

text
$ mcpvault add supabase
Label: work
Description: Day job, prod + staging
Personal Access Token: sbp_••••••••••••••••••••
✓ Validated against api.supabase.com (2 organizations, 7 projects)
✓ Saved.

#Tools exposed

• supabase_list_projects
• supabase_run_sql
• supabase_list_tables
• supabase_get_logs
• supabase_list_organizations

#Notes

• supabase_run_sql will execute arbitrary SQL against the active project. Treat it like prod credentials.

#Switch to this account

In any chat client wired to mcpvault, ask:

Switch to my <label> Supabase account.

The vault server's activate_account tool flips the active label. Wrappers re-read it on the next call — no restart.