Supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Description from the maker (original English)
Find why a PostgreSQL query is slow from its EXPLAIN output, without a database connection.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"slowplan": {
"command": "npx",
"args": [
"-y",
"slowplan",
"serve"
]
}
}
}Run this in your terminal
claude mcp add slowplan -- npx -y slowplan servePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"slowplan": {
"command": "npx",
"args": [
"-y",
"slowplan",
"serve"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"slowplan": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"slowplan",
"serve"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account GillMacedo, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP server and CLI that reads PostgreSQL `EXPLAIN` output and tells you where the time goes and what to try first. It works from the plan text alone, so it never connects to your database.
A long EXPLAIN ANALYZE is hard to read, and a mistake is easy: Postgres reports per-worker averages under parallel plans, and the slowest-looking node often isn't where the time went. slowplan works out the real time for each step, and ranks problems such as sequential scans throwing away rows, wrong row estimates, sorts and hashes spilling to disk, and nested loops run many times.
EXPLAIN ANALYZE output."As a Claude Code plugin:
claude plugin marketplace add GillMacedo/slowplan claude plugin install slowplan@slowplan-marketplace
As an MCP server, for any client:
{"mcpServers": {"slowplan": {"command": "npx", "args": ["-y", "slowplan@0.1.0", "serve"]}}}
As a CLI, with Node 18 or newer:
npx slowplan review plan.txt
Or with Go 1.27 or newer: go install github.com/GillMacedo/slowplan@latest.
Get a plan with EXPLAIN (ANALYZE, BUFFERS) , in text or JSON. `ANALYZE` really runs the query, so wrap anything that writes in a transaction you roll back.
Here's a real plan from PostgreSQL 17, on made-up tables:
$ make demo Execution 48.9 ms, planning 0.3 ms
Where the time goes: 80.8% 39.5 ms Bitmap Heap Scan on orders 3.9% 1.9 ms Bitmap Index Scan on orders_status_idx
HIGH PG102 Bitmap Heap Scan on orders The index doesn't cover the whole filter. Read and threw away 84857 rows to keep 857, using filter (bucket = 7). Try: Candidate to test: CREATE INDEX CONCURRENTLY ON orders (bucket), or add these columns to the index in use.
These are leads from one run. Test a fix on realistic data before relying on it.
To check a change, compare the plans from before and after:
slowplan compare before.txt after.txt
On a real example in examples/, adding the index that slowplan suggested took a query from about 25 ms to 0.1 ms.
Add --json for JSON, or --fail-on high to exit 1 in CI. Use - to read from stdin.
| Rule | Finds |
|---|---|
| PG101 | A sequential scan throwing away most of the rows it reads |
| PG102 | An index that doesn't cover the whole filter |
| PG103 | A join producing rows and then throwing them away |
| PG104 | A bitmap recheck throwing away many rows |
| PG105 | Row estimates off by 10 times or more |
| PG106 | A nested loop's inner side running 1,000 times or more |
| PG107 | A sort spilling to disk |
| PG108 | A hash table split into batches on disk |
| PG109 | Fewer parallel workers than planned |
| PG110 | An index-only scan still visiting the table often |
| PG111 | A bitmap that became lossy |
| PG112 | Reading about 80 MB or more from outside shared buffers |
| PG113 | Planning slower than running the query |
| PG114 | JIT taking 100 ms or more |
Severity comes from the share of the query's time: high is 20% or more, and low is under 5% or under 1 ms. These thresholds are judgment calls.
| Tool | Does |
|---|---|
postgres_plan_review | Reviews one plan, from text or a file |
postgres_plan_compare | Compares plans from before and after a change |
slowplan says so.slowplan stays on your machine, but your MCP client sends tool results to its model.How do I read EXPLAIN ANALYZE output? Give it to slowplan, which shows where the time goes.
Why is Postgres doing a sequential scan? Often there's no useful index, or the filter keeps so many rows that an index wouldn't help. PG101 shows how many rows were thrown away.
How do I find out if a sort or hash is using disk? PG107 and PG108 flag them.
How is this different from pev2 or postgres-mcp? pev2 is a visualizer for people. postgres-mcp connects to a live database. slowplan gives an agent ranked findings from plan text, with no database access.
PG101, PG102, PG104 to PG112 fired on real plans from a PostgreSQL 17 database with made-up tables, which are in examples/ in both JSON and text. PG103, PG113 and PG114 are only tested on written examples. MCP tool calls were tested through the MCP Inspector. It hasn't been used on a real production query yet.
Contributions are welcome, from people and from people working with AI agents. See CONTRIBUTING.md. Good first issues are listed here.
feat: goes under Added and fix: under Fixed.make test must pass. Changes over 30 lines need a linked open issue (Closes # ), and a PR can have at most 800 changed lines. If something is missing, a comment tells you what to fix.This project was largely generated with Claude Code and reviewed by its maintainer.
I'm Giulliano Macedo, and I build developer tools at GoTech Solutions. Follow along or get in touch:
If slowplan found your slow query, a star helps others find it.
Built by Giulliano Macedo, GoTech Solutions · LinkedIn · X