Triagic + Supabase: ticket investigations over your database, read-only
Query one Supabase project's tables, read its logs and security advisors. Runs the official server with --read-only, so SQL executes in a read-only transaction and the migration, branching and deploy tools are absent. Triagic connects to Supabase from the desktop app on each member's machine, with a credential you configure, and shows every call it makes while it investigates a ticket. Nothing is copied out of Supabase.
What you can ask
- Look up account acme-labs in Supabase and tell me why their last export failed
- In Supabase, how many orders for org 8412 are stuck in a non-terminal state right now?
- Which rows in Supabase changed for user 51930 in the last 24 hours?
- Compare the Supabase record for invoice INV-2291 with what the customer says they see
- Does Supabase show the same plan for this account as the billing system does?
What the agent can do
These are the 7 tools Triagic exposes from the Supabase MCP server. Anything else the server lists is dropped at connect time.
- search_docs
- list_tables
- list_extensions
- list_migrations
- query_logs
- get_advisors
- execute_sql
Connect in three steps
- 1
Mint a read-only credential in Supabase
Create a dedicated user or token that can only read. Started with --read-only so SQL runs in a read-only transaction; migration, branching and deploy tools are not offered.
- 2
Add it in the Triagic portal
Integrations, then Add shared data source, then Supabase.
- Personal access token: supabase.com/dashboard/account/tokens → Generate new token. It inherits its owner's organization access. The project's anon and service_role keys are not accepted here.
- Project ref: Project Settings → General → Reference ID, also the subdomain of the project's …supabase.co URL. One configuration is one project; add a second instance for a second project.
- 3
Let a desktop pick it up
Saving validates the shape of what you typed. The first desktop app to sync starts Supabase locally and reports running or degraded with the error text.
Field-by-field setup, TLS options and the error table: Supabase in the docs.
Read-only, by construction
Started with --read-only so SQL runs in a read-only transaction; migration, branching and deploy tools are not offered.
FAQ
- Can Triagic change anything in Supabase?
- No. Started with --read-only so SQL runs in a read-only transaction; migration, branching and deploy tools are not offered. Give it a read-only credential as well, so the guarantee does not rest on one layer.
- What do I need to connect Supabase?
- Personal access token, Project ref. The desktop app on a member's machine starts the connection; the portal never holds a live process.
- Does Supabase cost extra?
- No. Every connector is included in the seat price. Start a 14-day trial without a card.
Related integrations
- MongoDBQuery collections and inspect documents behind a ticket.
- PostgreSQLBrowse schemas and run read-only SQL against a Postgres database.
- MySQLBrowse every database, table and schema the credentials can reach. Read-only: there is no tool that runs a statement you write.
- RedisInspect keys and cached values. Read-only: the server's write tools are not exposed.
Try it on your own Supabase
No card. Install the desktop app, connect Supabase read-only, and triage a real ticket this afternoon.