Home / MCP registry index / Topics / Supabase
Supabase MCP servers, with their tools checked
Every server in the official MCP registry that mentions Supabase, with a public endpoint, read the way an MCP client reads it and checked for tool poisoning. The list updates as the registry does, and each server is read again every week.
8 listed. We have read the tools of 2 so far; the others want credentials first, could not be reached, or are still waiting for their first read.
Database servers can read your data and often change it. Check whether the tools are read-only before you connect one to a real database.
| Supabase io.github.mcp-dir/supabase-mcp | 35 tools, nothing matched 2026-10-22 |
| VibeRaven Guides io.github.ohad6k/viberaven-guides | 3 tools, nothing matched 2026-10-22 |
| Ekwo OS — open source accounting: ledger, invoices and VAT on your own Supabase or Postgres ai.ekwo/mcp | needs credentials to list tools 2026-10-21 |
| ai.waystation/supabase ai.waystation/supabase | not reachable 2026-10-22 |
| Scribase com.scribase/scribase | not read yet |
| Supabase com.supabase/mcp | not read yet |
| Ship Check com.uxcontinuum/ship-check | not read yet |
| Supabase URL Shape io.github.sadri-dridi/supabase-url-shape | not read yet |
Choosing one
Open a server's page to see the tools it advertises, whether it sets instructions for the model, and our latest read. Here, 2 of the servers shown matched none of our tool-poisoning rules on their last read. A clean read means our rules found nothing, not that a server is harmless; still check what access it asks for. To check one that is not listed, paste its URL into the free MCP server check.
Related: Postgres · MySQL · MongoDB · Redis · SQLite · Database · Spreadsheet · all topics