can ai see my supabase service role key

Only if a human explicitly asks for it. The key tool redacts the service role key by default and returns the anon key and project URL, plus a flag saying whether a service role key exists.

supabase mcp or native integration which is better

Supabase is both. The native tools give you the guarded shape described here (bounded selects, filter-required deletes, redacted keys) with approval gates in the same flow as every other action.

Supabase Strawberry

The eleven-o’clock support question, answered in one ask

A companion lists the tables, describes the two that matter, reads the customer’s rows, and reports the null plus the two other accounts with the same shape.

A customer says their invite link stopped working. You have their email, a support thread and a suspicion about a foreign key. In the dashboard that is four steps and ten minutes, at eleven at night, and it is a different customer next week.

A companion does it in one ask. It lists the tables with their row-level security state, describes the two that matter so it has the real column names and foreign keys, reads the rows, and reports what it found. You do not have to know the schema before you ask.

Answer a support question from the database

It lists the tables, describes the two that matter, selects the customer’s rows, and reports the null, the row it should have pointed at, and the two other accounts with the same shape.

Selects default to a hundred rows unless you ask for more, which keeps an exploratory question from turning into a table scan. Describing the schema is a step it takes rather than an assumption it makes.

What does running as the service role mean for you?

Selects, inserts, updates, deletes and raw SQL all go through the Management API as the service role, so they see what is in the table rather than what one user is allowed to see. That is what makes this usable during support work, and it is why you decide which project to connect.

The guards live in the tools. Updates and deletes require an equality filter, or an explicit force flag for a table-wide operation. Deleting rows is confirmed before it runs. Point it at a staging project when staging answers the question.

List tables with RLS state and policy count; an RLS table with zero policies is deny-all.
Describe columns, primary keys, foreign keys and indexes before writing anything.
Row tools require a where clause, or an explicit force flag, for updates and deletes.
Secrets can be listed and set; their plaintext values are never returned, only a hash.

Native tools or the MCP server?

Supabase is both a native integration and a known MCP app, so there are two doors into the same project and the difference is what you get on the other side.

The native tools are shaped for this product: a described table, a bounded select, a guarded delete, a redacted key, with approval gates wired into the same flow as every other companion action. The MCP path gives you whatever that server exposes, on the vendor’s release schedule.

Write the answer back into the ticket

The support thread, the payment record and the row, read together and written up as a reply in the ticket rather than a result grid only you can see. That is data extraction across systems, and it is the version of the eleven-o’clock question that ends with the customer hearing back.

Edge functions can be listed and inspected, including a ready-to-call invocation URL. Schema changes stay in migrations reviewed like code. The same read-and-operate split runs through the Vercel tools.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. It lists tables, describes their schema, and reads rows with filters, ordering and paging, or runs raw SQL when the question needs it. Selects are bounded to 100 rows unless you ask for more.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed August 20, 2026 · Canonical facts for AI agents