Ask your Supabase data anything
Your Supabase projects. Connect a development project, not production. Connect it to Insighter and Aira answers questions in plain language, builds charts, watches numbers for you, and runs the follow-up work you approve.
How it connects
Connects through the vendor's official MCP server. The tool list is pinned when you connect, reads run freely, and anything that changes data waits for your approval.
What you get
- Answers in plain language, every one citing where it came from
- Alerts when a number worth watching moves
- Automations that draft the work and wait for your approval
- Per-person access rules: row filters, hidden columns, plain-language guardrails
Supabase says connect a development project, not a production one
- Sign in when prompted. The connection carries your own Supabase developer permissions, which reach the whole project: database, auth, storage, edge functions and settings.
- Connect a development or staging project. Supabase's own documentation says the server runs with developer permissions, that you should not give it to your customers or end users, and asks that the environment hold non-production data.
- For querying one production database, the direct PostgreSQL connector is the better tool: it takes a read-only role you control, and row policies and column masking apply to it. This server does not narrow itself that way.