
About
Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas.
name: supabase-automation description: "Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas." risk: critical source: community date_added: "2026-02-27"
Supabase Automation via Rube MCP
Automate Supabase operations including database queries, table schema inspection, SQL execution, project and organization management, storage buckets, edge functions, and service health monitoring through Composio's Supabase toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Supabase connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsupabase - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitsupabase - If connection is not ACTIVE, follow the returned auth link to complete Supabase authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Query and Manage Database Tables
When to use: User wants to read data from tables, inspect schemas, or perform CRUD operations
Tool sequence:
SUPABASE_LIST_ALL_PROJECTS- List projects to find the target project_ref [Prerequisite]SUPABASE_LIST_TABLES- List all tables and views in the database [Prerequisite]SUPABASE_GET_TABLE_SCHEMAS- Get detailed column types, constraints, and relationships [Prerequisite for writes]SUPABASE_SELECT_FROM_TABLE- Query rows with filtering, sorting, and pagination [Required for reads]SUPABASE_BETA_RUN_SQL_QUERY- Execute arbitrary SQL for complex queries, inserts, updates, or deletes [Required for writes]
Key parameters for SELECT_FROM_TABLE:
project_ref: 20-character lowercase project referencetable: Table or view name to queryselect: Comma-separated column list (supports nested selections and JSON paths likeprofile->avatar_url)filters: Array of filter objects withcolumn,operator,valueorder: Sort expression likecreated_at.desclimit: Max rows to return (minimum 1)offset: Rows to skip for pagination
PostgREST filter operators:
eq,neq: Equal / not equalgt,gte,lt,lte: Comparison operatorslike,ilike: Pattern matching (case-sensitive / insensitive)is: IS check (for null, true, false)in: In a list of valuescs,cd: Contains / contained by (arrays)fts,plfts,phfts,wfts: Full-text search variants
Key parameters for RUN_SQL_QUERY:
ref: Project reference (20 lowercase letters, pattern^[a-z]{20}$)query: Valid PostgreSQL SQL statementread_only: Boolean to force read-only transaction (safer for SELECTs)
Pitfalls:
project_refmust be exactly 20 lowercase letters (a-z only, no numbers or hyphens)SELECT_FROM_TABLEis read-only; useRUN_SQL_QUERYfor INSERT, UPDATE, DELETE operations- For PostgreSQL array columns (text[], integer[]), use
ARRAY['item1', 'item2']or'{"item1", "item2"}'syntax, NOT JSON array syntax'["item1", "item2"]' - SQL identifiers that are case-sensitive must be double-quoted in queries
- Complex DDL operations may timeout (~60 second limit); break into smaller queries
- ERROR 42P01 "relation does not exist" usually means unquoted case-sensitive identifiers
- ERROR 42883 "function does not exist" means you are calling non-standard helpers; prefer information_schema queries
2. Manage Projects and Organizations
When to use: User wants to list projects, inspect configurations, or manage organizations
Tool sequence:
SUPABASE_LIST_ALL_ORGANIZATIONS- List all organizations (IDs and names) [Required]SUPABASE_GETS_INFORMATION_ABOUT_THE_ORGANIZATION- Get detailed org info by slug [Optional]SUPABASE_LIST_MEMBERS_OF_AN_ORGANIZATION- List org members with roles and MFA status [Optional]SUPABASE_LIST_ALL_PROJECTS- List all projects with metadata [Required]SUPABASE_GETS_PROJECT_S_POSTGRES_CONFIG- Get database configuration [Optional]SUPABASE_GETS_PROJECT_S_AUTH_CONFIG- Get authentication configuration [Optional]SUPABASE_GET_PROJECT_API_KEYS- Get API keys (sensitive -- handle carefully) [Optional]SUPABASE_GETS_PROJECT_S_SERVICE_HEALTH_STATUS- Check service health [Optional]
Key parameters:
ref: Project reference for project-specific toolsslug: Organization slug (URL-friendly identifier) for org toolsservices: Array of services for health check:auth,db,db_postgres_user,pg_bouncer,pooler,realtime,rest,storage
Pitfalls:
LIST_ALL_ORGANIZATIONSreturns bothidandslug;LIST_MEMBERS_OF_AN_ORGANIZATIONe
