Supabase MCP integration
Query Supabase tables, inspect schemas, and bring live Postgres context into model workflows through one managed MCP connection.
Supabase is one of the highest-intent MCP providers for engineering teams because it turns live product data into usable model context. Connexsus wraps the connection, vault storage, and project assignment so teams can use Supabase safely across multiple clients.
Install path
This provider validates connection inputs before saving them so teams can catch configuration errors before enabling MCP tools.
What you can do with Supabase
- Inspect a schema before generating SQL.
- Verify production data shape during debugging.
- Cross-check auth or storage state while triaging app behavior.
Sample prompts
Available capabilities
4 toolssupabase_list_tables
List all tables in the connected Supabase database.
supabase_describe_table
Show a table schema with column metadata (supports schema-qualified names like public.users).
supabase_query_table
Query rows from a table with select/filter/order/limit arguments.
supabase_execute_sql
Execute SQL via RPC helper function. Use read_only by default.
FAQ
Does Connexsus store my Supabase credentials securely?
Yes. Supabase credentials are stored using the existing encrypted vault model used by Connexsus integrations.
Can I control which schema is queried?
Yes. Connexsus keeps schema support metadata and uses preferred and exposed schema resolution during Supabase operations.
Is Supabase public data exposed on SEO pages?
No. Public SEO pages only use published catalog metadata, never project-scoped database state.
Auth and workspace model
Connexsus separates public provider information from private runtime state. Teams install the provider after sign-in, assign it to a project, and then expose tools to supported MCP clients from one managed gateway endpoint.