Most attempts to use agents for monitoring fail for the same reason: the brief is too vague. "Monitor and fix" is not a job description. An expert needs a defined scope, the right data sources, and a clear format for what they report back.
We shipped a few things to make this even more powerful with Supabase's AI tooling.
Hire an agent#
The Hire an agent guide defines four roles, each with a prepared prompt and setup instructions for Claude Routines, Codex scheduled tasks, or Cursor Automations:
- Health — API and Auth error rates, connection pressure, instance state
- Security — Security Advisor findings, RLS gaps, Auth 4xx patterns
- Performance — slow queries, lock waits, long-running sessions, Performance Advisor
- Capacity — request, error, storage, and connection growth against baselines
Each prompt scopes the agent to a specific job, runs across a fresh context, and routes findings through your existing integrations — Linear, Slack, wherever your team tracks work. Copy the prompt as-is or adapt it. It runs in any environment that supports MCP, not just the ones listed.
The Supabase plugin#
The MCP server already covers a broad range of Supabase tooling — database management, debugging, Edge Functions, branching, and more. A new query_logs tool extends that with structured access to logs across all services: API, Auth, Storage, Edge Functions, and Postgres. Everything you'd debug with a SQL query against your instance, your agent can now reach through MCP.
The agent skills pair with that data: they teach agents how to use Supabase correctly, pulling from a docs structure rebuilt so agents find the right material reliably. More knowledge on what the data means and where to look.
Both are part of the Supabase plugin — the MCP server and skills bundled for a single install.
Get started#
Read the Hire an agent guide, pick a role, and copy the prepared prompt into your environment of choice. To use the full Supabase toolset, install the plugin from the AI tools page.