Supabase lets your coding agent watch production for you

Supabase shipped five pieces today aimed at one problem: teams usually hear about a production issue from users before they find it in logs. The centrepiece is a new query_logs MCP tool that runs read-only SQL against a project’s logs, up to 24 hours per request, so an agent can aggregate and join across API, Auth, Storage and Edge Function events without you writing the query by hand.

Alongside it: a Health tab in Advisors that flags unusually high error rates, and a Database Connections page, on by default for every project including self-hosted, that shows blocked queries, long-running transactions and lock holders, with a cancel button built in. Supabase also published four ready-made prompts, Health and Performance hourly, Security and Resources daily, that you point at a scheduled Claude routine, a Codex scheduled task or a Cursor automation. Setup is one MCP connection:

claude mcp add --scope project --transport http supabase "https://mcp.supabase.com/mcp?project_ref=abc123&read_only=true"

Why it matters: this turns “check if anything is wrong” from a dashboard habit into something you can schedule and forget, and because the MCP connection is read-only, you can hand it to an agent without worrying about it changing production. The 24-hour log window per query is the practical limit to know about if you’re debugging something older.