---

name: supabase category: integration-connectivity/mcp-integrations version: 1.0.0 description: Complete guide to using Supabase MCP servers with Claude Code author: blackbox5/mcp verified: true tags: [mcp, supabase, database, storage]

Supabase MCP Server Skills

1. SISO Internal Supabase (Global) - avdgyrepwrvsvwgxrccr
2. Lumelle Supabase (Project) - tmsbyiwqzesmirbargxv

Claude automatically detects which Supabase to use based on the current project directory.

Always start with exploration (list tables, describe schema) before making changes. Use transactions for complex operations.

<available_skills> <skill_group name="Database Query"> Execute raw SQL queries Query the users table for all active users The SQL query to execute Select rows with filtering Get all products where price > 100 Table name Filter conditions (optional) Specific columns (optional) Order by column (optional) Maximum rows (optional) Insert new rows Insert a new user with email john@example.com Table name Object with column names and values Update existing rows Update user john@example.com to set status to inactive Table name Columns to update Filter condition Delete rows from table Delete all users where status is 'deleted' Table name Filter condition </skill_group>

<skill_group name="Schema Management"> List all tables in database Show me all tables in the database Get table schema Describe the users table Column names, data types, constraints, indexes Get foreign key relationships Show relationships for the orders table </skill_group>

<skill_group name="Advanced Operations"> Call PostgreSQL function Execute the function get_user_stats with user ID 123 Subscribe to real-time changes Subscribe to changes in the notifications table Upload file to Supabase Storage Upload image.png to the avatars bucket Download file from Supabase Storage Download avatar.jpg from the avatars bucket </skill_group> </available_skills>

<best_practices> Use natural language - Claude converts to SQL Start with supabase_list_tables to understand structure Use descriptive column names in queries Ask for explanations of complex queries Use transactions for complex operations </best_practices>

<anti_patterns> Run DELETE without WHERE clause Modify schema directly in production Insert duplicate primary keys Forget to back up important data </anti_patterns>

<multi_database_usage> <automatic_detection> Working in Lumelle project Uses Lumelle Supabase (tmsbyiwqzesmirbargxv) Get all products from Lumelle database </automatic_detection> <automatic_detection> Working in any other project Uses SISO Internal Supabase (avdgyrepwrvsvwgxrccr) Get all internal users from SISO database </automatic_detection> <explicit_selection> Need to specify database explicitly In the SISO database, get all users In the Lumelle database, get all orders </explicit_selection> </multi_database_usage>

<integration_notes> Project-specific notes:

Lumelle Project Supabase:

• Project: Lumelle partnership platform
• Used for: Products, orders, customer data
• Location: Available only in Lumelle project directory

SISO Internal Supabase:

• Project: SISO internal operations
• Used for: Internal data, analytics, operations
• Location: Available globally in all projects </integration_notes>

<error_handling> Permission denied - Check your Supabase access token - Verify RLS policies on the table

Connection timeout - Check your internet connection - Verify Supabase URL is correct

Query returns no results - Use supabase_describe_table to verify column names - Check if data exists in the table - Verify filter conditions </error_handling>

<related_skills> filesystem github </related_skills>

<see_also> Supabase documentation: https://supabase.com/docs RLS policies: https://supabase.com/docs/guides/auth/row-level-security </see_also>