supabase-mcp-server
Query MCP enables end-to-end management of Supabase via chat interface: read & write query executions, management API support, automatic migration versioning, access to logs and much more.
Runssource: GitHubPythonApache-2.0commit bca07008fe46
Python, Apache-2.0 licensed. The project labels itself: cursor, model context protocol, supabase and windsurf.
supabase-mcp-server runs. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Supabase MCP server installs cleanly, all 191 tests pass, and the server binary starts and answers the MCP initialize/tools-list handshake with 12 registered tools.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 60 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- test_comprehensive_spec_retrieval failed: fresh ApiSpecManager fetched the live remote spec (147 schemas) which lacks FunctionResponse, while the bundled fallback spec has it4 minutes
- ImportError: No module named 'mcp.server.fastmcp' because pip resolved mcp 2.3.0 which removed the FastMCP v1 API3 minutes
- pytest failed to start: pyproject.toml uses both [tool.pytest] and [tool.pytest.ini_options] simultaneously2 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- .venv/bin/python -m pytest -p no:cacheprovider exited 0 with 191 passed; MCP stdio probe: initialize returned {"name":"supabase","version":"1.30.0"} and tools/list returned 12 tools
- Model tokens used
- 1,465,352
- Exact commit tested
- bca07008fe46
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Summary**
Installed the repo from source (`pip install -e .` in a fresh `python3.12` venv since `uv` is absen…
**Errors found and fixed**
- `pyproject.toml` had both `[tool.pytest]` and `[tool.pytest.ini_options]`, which pytest rejects o…
- Unpinned `mcp[cli]>=1.4.1` resolved to mcp 2.3.0, which removed the `mcp.server.fastmcp` API this…
- The comprehensive API spec test silently fetched the live remote spec (network available) whose c…
**Verification (all observed here)**
- `pip install -e .` completed successfully with wheel build.
- `pip check` → "No broken requirements found."
- Full suite: `pytest` → **191 passed** (was 3 failed / 188 passed before fixes).
- Real binary: `supabase-mcp-server --help` starts, initializes all services, prints "All services …
- MCP stdio handshake probe: `initialize` → serverInfo `{"name": "supabase", "version": "1.30.0"}`;…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 3 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 3 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.30 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.16 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/supabase-mcp-server)Questions
- Does supabase-mcp-server run?
- Yes. supabase-mcp-server runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test supabase-mcp-server?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bca07008fe46. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test supabase-mcp-server?
- The run that produced this verdict cost $0.30: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does supabase-mcp-server take to install?
- 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does supabase-mcp-server need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing supabase-mcp-server?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for supabase-mcp-server?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.