pickfit

BrowseMCP servers

Supabase MCP Server

MCP server that connects AI assistants to Supabase projects to manage tables, fetch config and query data.

How far pickfit got

pickfit hasn’t verified Supabase MCP Server yet, so there are no tested install steps.

What follows comes from its README only.

Use it

Before you install: known vulnerabilities

pickfit found 4 known high or critical vulnerabilities (5 findings, one per affected package version) in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.

  • npm:@modelcontextprotocol/node 2.0.0 MCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length (GHSA-f897-62hf-6gxq, high, fixed in 2.1.0)
  • npm:@modelcontextprotocol/server 2.0.0 MCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation (GHSA-46jr-4wx8-v453, high, fixed in 2.3.0)
See 3 more

You need first

  • Needs the network
  • Keys or accounts: Supabase account

What it does

pickfit hasn’t run it yet, so these come from the README only.

  • Manage database tables and migrations
    Not tested
  • Run SQL queries on a project
    Not tested
  • Deploy and manage Edge Functions
    Not tested
  • Search the Supabase documentation
    Not tested

Good for

  • list the tables in a Supabase database from an AI assistant
  • apply database migrations through an AI agent
  • deploy Supabase Edge Functions from an AI assistant
  • generate TypeScript types from a database schema

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.