Check Supabase Health
For an indie dev onboarding to a new Supabase project, or validating an existing one, who wants a one prompt health check. It verifies connectivity, inspects tables, columns, and constraints, flags drift against an expected schema, and can optionally apply a migration.
SupabaseThe grind
Silent schema drift
Here's what doing this by hand looks like today, and why it doesn't scale.
- Schema drift builds up silently until production breaks.
- Nobody runs connectivity or index checks until there is an outage.
- Digging through the dashboard for a health report wastes a morning.
MewCP collapses all of this into one prompt. Here's what that looks like.
The flow
8 steps · 1 server
Your agent runs it end-to-end
Ping the project and confirm the status is active and healthy.
List the tables in the public schema.
For each table, list the columns with their types, nullability, and defaults.
Check the constraints, including primary keys, foreign keys, and unique constraints.
Check the row level security status.
If an expected schema is provided, compute the drift, including missing tables, missing columns, type mismatches, and missing row level security.
Compose a health report.
If applying a migration is turned on and drift is found, author a DDL migration.
The payoff
Know your database is healthy
A single prompt returns a health scorecard covering connectivity, schema drift, and missing indexes, before your users notice anything.
Paste this into Claude, Codex, or any MCP-connected agent. It'll connect your apps and run the task from start to finish.
Run it yourself
Copy the prompt
Goal: Check Supabase Health MCP servers needed (connected through MewCP): Supabase Steps: 1. Ping the project and confirm the status is active and healthy. 2. List the tables in the public schema. 3. For each table, list the columns with their types, nullability, and defaults. 4. Check the constraints, including primary keys, foreign keys, and unique constraints. 5. Check the row level security status. 6. If an expected schema is provided, compute the drift, including missing tables, missing columns, type mismatches, and missing row level security. 7. Compose a health report. 8. If applying a migration is turned on and drift is found, author a DDL migration. Check with me before sending any message or changing data in a connected app.
