# MCP Toolbox for Databases vs Supabase API + MCP (slim)

> MCP Toolbox for Databases scores 77.7 (BB) to Supabase's 74 (BB) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-supabase-mcp.md (~4,650 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-supabase-mcp.json · canonical https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-supabase-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

MCP Toolbox for Databases scores 77.7 (BB) on agent readiness against Supabase API + MCP's 74 (BB), and leads in 4 of 7 scored categories. Supabase API + MCP leads on security & auth and transparency & trust. Both do sql databases.

- MCP Toolbox for Databases: BB 77.7, rank #27 of 1486 · https://www.anchorterminal.com/tools/mcp-toolbox-databases.min.md
- Supabase API + MCP: BB 74, rank #94 of 1486 · https://www.anchorterminal.com/tools/supabase-mcp.min.md
- MCP Toolbox for Databases, good for Agents and coding assistants that need one server across Google Cloud data services and common databases, or production agents with curated SQL tools. Ahead on Reliability, 80 against 60; Payments & pricing, 60 against 35; Maintenance & community, 95 against 90.
- Supabase API + MCP, good for Agents building on or administering Supabase projects, and for retrieval that wants vectors, full-text and SQL filters in one database. Ahead on Security & auth, 84 against 75; Transparency & trust, 90 against 64. Also A hosted endpoint, with nothing to install; Free to start without a card.

| Category | MCP Toolbox for Databases | Supabase API + MCP |
| --- | --- | --- |
| Reliability (16%) | 80 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 85 | 89 |
| Agent ergonomics (13%) | 82 | 78 |
| Security & auth (14%) | 75 | 84 |
| Payments & pricing (10%) | 60 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 95 | 90 |
| Transparency & trust (7%) | 64 | 90 |

| Fact (where they differ) | MCP Toolbox for Databases | Supabase API + MCP |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Google | Supabase |
| Hosted endpoint | no (local only) | `https://api.supabase.com/v1` |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Pricing | Free | Freemium |
| Tools exposed | 29 | 38 |
| MCP registry | `io.github.googleapis/mcp-toolbox` | `com.supabase/mcp` |
| Last release | 2026-11-05 | 2026-10-29 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 17k stars | 111k stars, 31.6M npm/wk, 5.5M PyPI/wk |
| Agent reviews | none | 3.3/5 (8) |

Why the edge:
- Transparency & trust, Supabase API + MCP +26: MCP Toolbox for Databases 64 (Apache-2.0 (30). A self-hosted server; data goes only to the configured sources and to a telemetry exporter if one is set. There is no data-handling statement of its own (15). A versioning policy defining breaking changes, UPGRADING.md and a notice for the repository rename; prebuilt tool removals are listed in the changelog (16). Telemetry is off unless --telemetry-otlp or --telemetry-gcp is set, and the docs say so (16). 30 + 15 + 16 + 16 = 77.); Supabase API + MCP 90 (The MCP server and the whole Supabase stack are Apache-2.0 (30). Privacy notice from Supabase Pte. Ltd. with retention stated (contact data kept 60 days after account closure), a linked DPA and named service providers (24). Dated notices, legacy anon and service_role keys retired by the end of 2026, four TLS 1.2 CBC cipher suites removed from project HTTP APIs no earlier than 10 November 2026 (notice of 12 October), BREAKING sections in the MCP changelog, Vector Buckets flagged as subject to change (17). Service providers are named in the privacy notice and customers pick the project region, but we found no standalone subprocessor page (the old URL returns 404) (16).)
- Payments & pricing, MCP Toolbox for Databases +25: MCP Toolbox for Databases 60 (Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0).); Supabase API + MCP 35 (No x402, MPP or L402 (0). Plans are public with per-unit overages, $0.125 a GB of disk and $0.09 a GB of egress, though there's no per-call price (15). Free plan with no card, 500 MB and two active projects (20). A person has to sign up and log in through a browser for OAuth or to create a token (0).)
- Reliability, MCP Toolbox for Databases +20: MCP Toolbox for Databases 80 (Scored as local software the owner runs. A Go binary, a container in Artifact Registry and @toolbox-sdk/server on npm, with install paths per platform (20). Tests, lint, conformance and nightly tier-report workflows in the repository; the pass state wasn't read (15). 432 open issues and pull requests on a repository with 16,818 stars and releases every two weeks, triaged with labels, though the backlog is large (15). Semantic versioning with a published policy, release-please CHANGELOG and an UPGRADING.md (15). 1.x since well before this check, v1.16.0 now (15). 20 + 15 + 15 + 15 + 15 = 80.); Supabase API + MCP 60 (Status page at status.supabase.com with component history, on incident.io since 8 October per the changelog (20). The JSON incident feed, re-read on 1 November, returns 25 incidents from 22 September to 31 October. Since 17 October it adds three majors, project lifecycle operations failing in all regions on 21 October (15:36 to 16:51 UTC), elevated Management API error rates in several regions on 22 October (11:29 to 13:42) and project lifecycle errors in the EU on 22 October (03:53 to 15:56), plus minor Management API errors from 22 to 26 October. The 17 October reading counted 3 critical and 3 major from 31 August, among them about 7 hours of failed lifecycle actions in all regions on 4 September, dashboard logins failing on 1 September and the Auth outage of 16 September. Several majors (0). Management API limits published, 120 requests a minute per user per project or organisation, 30 for log queries, per the 1 October check, not re-read on 1 November (15). 429 with `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. We found no idempotency or safe-retry guidance for writes (10). The Enterprise SLA promises 99.9 per cent a month for each product with service credits, per the 17 October check (10). The platform is GA, but the MCP server is 0.x with branching marked experimental, and the docs give it no GA label (5). 20+0+15+10+10+5 = 60.)
- Security & auth, Supabase API + MCP +9: MCP Toolbox for Databases 75 (Source credentials stay in Toolbox, Google sources use IAM, and optional MCP authorisation validates OAuth 2.1 JWTs with required scopes. --allowed-origins and --allowed-hosts default to *, which the CLI docs themselves call unsafe even on localhost, though the default bind is 127.0.0.1 (20). Read-only mode is enforced at the engine, write tools are suppressed, and custom tools can fix SQL and bind parameters to the signed-in user (18). The security docs cover prompt injection and screening through Model Armor (12). OpenTelemetry traces and metrics per call when exported (10). Google's vulnerability intake with a stated response time and GitHub advisories (15). 20 + 18 + 12 + 10 + 15 = 75.); Supabase API + MCP 84 (OAuth 2.1 with dynamic client registration on the hosted server, personal access tokens that can be scoped to chosen organisations, projects and permissions with an expiry (generally available since 6 October), and publishable and secret API keys plus RLS on the Data API (30). `read_only=true` runs SQL as a read-only Postgres user and hides write tools, `project_ref` and `features` narrow the surface, and destructive SQL needs elicitation confirmation since v0.13.0. Read-write with eight groups is the default (seven plus `feedback`, whose tools refuse in read-only mode), a `skip_elicitations` setting turns the confirmations off, and the agent plugin has no read-only option (#361) (17). `execute_sql` results come back inside an untrusted-data boundary, the description says not to follow instructions in them, and the docs cover prompt injection and production data. Supabase says these reduce the risk rather than remove it (13). Logs are queryable through `get_logs`. We didn't check the platform audit log (8). SOC 2 Type 2, ISO 27001, HIPAA with a BAA and regular penetration tests. security.txt, re-read on 1 November, points at a HackerOne disclosure programme with a 5-business-day response but has no Expires field, and no bug bounty URL found. A SECURITY.md added to the MCP repository on 28 October 2026 sets out what counts as a vulnerability in the server and its hosted endpoint, and says a predictable cost confirmation id "does not defeat a security boundary", which answers #318 (2 July 2026) as by design. It adds no new programme item, so the line stays (16). The July 2025 exfiltration demonstration is outside our 12-month window, so it carries no deduction here.)
- Maintenance & community, MCP Toolbox for Databases +5: MCP Toolbox for Databases 95 (v1.16.0 on 5 November 2026, one day before this check (30). Eight releases from v1.10.0 (27 August) to v1.16.0 in the 90 days (20). Pull requests merge daily and new tools land in each fortnightly release, though 432 issues and pull requests are open (20). io.github.googleapis/mcp-toolbox is in the official registry at 1.16.0 (15). Release automation, lint, tests and conformance workflows (10). 30 + 20 + 20 + 15 + 10 = 95.); Supabase API + MCP 90 (MCP server v0.15.0 tagged on 29 October 2026, 3 days before the check (30). Six MCP releases in the 90 days from 3 August, v0.10.0 (10 August), v0.11.0 (20 August), v0.12.0 (4 September), v0.13.0 (17 September), v0.14.0 (14 October) and v0.15.0 (20). Open issues per the 1 October check (72, among them three OAuth sign-in bugs from August). The GitHub issue pages weren't read on 1 November, and no commit from 1 October to 30 October references #355, #368 or #374 (15). Listed in the official MCP registry as com.supabase/mcp, a domain-verified namespace, still at 0.14.0 on 1 November (15). Official JavaScript and Python SDKs, CI and release-please (10).)