Supabase MCP Connector
Connect Sazabi to Supabase through MCP for database queries and management.
The Supabase MCP connector lets Chat query databases, manage authentication, and access Supabase features. This enables Sazabi to investigate issues that involve your Supabase data and apply changes when you ask it to.
About the Supabase MCP connector
The Supabase MCP connector gives Chat the ability to interact with Supabase on your behalf. With this connector, Chat can:
- Run ad-hoc SQL queries (
execute_sql) and apply migrations (apply_migration) - Query and modify database tables and configuration
- Manage authentication, edge functions, secrets, storage, and project settings
- Browse organizations, projects, branches, and logs
This connector is granted both read and write scopes on the Supabase Management API. Chat can mutate your Supabase resources when you instruct it to. Only connect Supabase projects you are comfortable letting Chat modify, and review proposed changes before approving them.
Prerequisites
Before connecting Supabase via MCP, make sure you have:
- A Sazabi account with admin permissions.
- A Supabase project with API access.
Connecting Supabase
Open MCP Connectors
Go to Settings -> MCP Connectors in the Sazabi dashboard.
Select Supabase
Find Supabase in the list of available connectors and click Connect.
Authorize access
You will be redirected to Supabase to authorize Sazabi. Review the requested permissions and click Authorize.
Verify connection
After authorization, you will be returned to Sazabi. The Supabase connector should show as connected with available tools listed.
Available tools
Once connected, the Supabase MCP connector provides tools to Chat for:
- Database queries and SQL execution (
execute_sql) - Schema migrations (
apply_migration) - Table and configuration management
- Authentication, edge functions, storage, and secrets management
- Project and organization browsing, including logs and advisors
Usage examples
With the Supabase MCP connector, you can ask Sazabi to:
Query the users table for recent signups
Check authentication logs for failed login attempts
What tables exist in the database?
Look up the order record for user abc123Security considerations
The Supabase MCP connector respects your Supabase row-level security (RLS) policies. Sazabi can only access data that your RLS policies allow.
Be careful when granting Supabase access. Review the permissions requested and ensure they align with your security requirements.
Troubleshooting
Connection failed
If the OAuth flow fails:
- Verify you have permission to authorize apps in your Supabase project.
- Check that your Supabase project has API access enabled.
- Try disconnecting and reconnecting.
Query failures
If queries fail:
- Verify the Supabase connector is still connected.
- Check that RLS policies allow access to the requested data.
- Ensure the table or resource exists.