A MCP server for the Ankr Advanced API
Free
Nothing to run from here
Supabase Utils is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP utilities
Quickstart
# 1 — run it from where its publisher ships it
npx -y @supabase/mcp-utils
# 2 — ask your agent something
> MCP utilities
Supabase Utils is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
SUAll 2 servers
Supabase2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Supabase Utils as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add supabase-utils-mcp -- npx -y @supabase/mcp-utilsReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
28 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Lists all organizations that the user is a member of.
Takes no parameters.
Example callreturns →
Gets details for an organization. Includes subscription plan.
Takes no parameters.
Example callreturns →
Lists all Supabase projects for the user. Use this to help discover the project ID of the project that the user is working on.
Takes no parameters.
Example callreturns →
Gets details for a Supabase project.
Takes no parameters.
Example callreturns →
Gets the cost of creating a new project or branch. Never assume organization as costs can be different for each. Always repeat the cost to the user and confirm their understanding before proceeding.
Takes no parameters.
Example callreturns →
Ask the user to confirm their understanding of the cost of creating a new project or branch. Call
Takes no parameters.
Example callreturns →
Creates a new Supabase project. Always ask the user which organization to create the project in. The project can take a few minutes to initialize - use
Takes no parameters.
Example callreturns →
Pauses a Supabase project.
Takes no parameters.
Example callreturns →
Restores a Supabase project.
Takes no parameters.
Example callreturns →
Lists all development branches of a Supabase project. This will return branch details including status which you can use to check when operations like merge/rebase/reset complete.
Takes no parameters.
Example callreturns →
Deletes a development branch.
Takes no parameters.
Example callreturns →
Merges migrations and edge functions from a development branch to production.
Takes no parameters.
Example callreturns →
Resets migrations of a development branch. Any untracked data or schema changes will be lost.
Takes no parameters.
Example callreturns →
Rebases a development branch on production. This will effectively run any newer migrations from production onto this branch to help handle migration drift.
Takes no parameters.
Example callreturns →
Lists all tables in one or more schemas. By default returns a compact summary. Set verbose to true to include column details, primary keys, and foreign key constraints.
Takes no parameters.
Example callreturns →
Lists all extensions in the database.
Takes no parameters.
Example callreturns →
Lists all migrations in the database.
Takes no parameters.
Example callreturns →
Applies a migration to the database. Use this when executing DDL operations. Do not hardcode references to generated IDs in data migrations.
Takes no parameters.
Example callreturns →
Executes raw SQL in the Postgres database. Use
Takes no parameters.
Example callreturns →
Gets a list of advisory notices for the Supabase project. Use this to check for security vulnerabilities or performance improvements. Include the remediation URL as a clickable link so that the user can reference the issue themselves. It
Takes no parameters.
Example callreturns →
Gets the API URL for a project.
Takes no parameters.
Example callreturns →
Generates TypeScript types for a project.
Takes no parameters.
Example callreturns →
Lists all Edge Functions in a Supabase project.
Takes no parameters.
Example callreturns →
Retrieves file contents for an Edge Function in a Supabase project.
Takes no parameters.
Example callreturns →
Deploys an Edge Function to a Supabase project. If the function already exists, this will create a new version. Example:\n\n${edgeFunctionExample}
Takes no parameters.
Example callreturns →
Lists all storage buckets in a Supabase project.
Takes no parameters.
Example callreturns →
Get the storage config for a Supabase project.
Takes no parameters.
Example callreturns →
Update the storage config for a Supabase project.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Supabase Utils costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 100 / 100
Release 0.7.0 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
VerificationOfficial
Surface digestnot in this report
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability blast radius | minimal | −0 | |
| publisher verification | official | −0 | |
| inspection depth | source | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Inspection depthsource
Registrynpm
Release readv0.7.0
Tools recoverednone
Findings raised0
Engine1.13.0
Scanned2026-08-25T21:33:25.089Z
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
The scan recovered no tool surface for this release, so there is no per-tool table here — the capability level above is the one it assigned to the package as a whole.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Package@supabase/mcp-utils
Registrynpm
Release scannedv0.7.0
Publisher verificationOfficial
Source repositorydeclared
Engine1.13.0
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.7.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.7.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Supabase Utils in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.