AgentSidekick

Better agent tooling for Supabase

Integration gap · Measured demandOverall 60.1 / 100 DERConfidence Medium DERCalculated

5,092 public GitHub issues mention "Supabase mcp" (checked 2026-11-21) SRC, while 47 indexed products mention Supabase DER. On the six weighted components it scores 60.1 of 100, confidence Medium, as of 2026-11-21.

Score breakdown

Contribution = weight × component score. The contributions add up to the overall score.

ComponentWeightScoreScore (0–100)ContributionKind
Demand0.2589.00.25 × 89.0 = 22.25Measured
Competition gap0.2016.00.20 × 16.0 = 3.20Measured
Monetisation0.2035.00.20 × 35.0 = 7.00Heuristic
Growth (relative)0.1578.00.15 × 78.0 = 11.70Measured
Feasibility0.1080.00.10 × 80.0 = 8.00Heuristic
Distribution0.1079.00.10 × 79.0 = 7.90Measured
Overall1.0060.05 → 60.1

Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.

Confidence: Medium

Rule: Medium when at least 50 GitHub issues mention the integration and at least 10 indexed products mention it; otherwise Low. Nothing is rated High.

What would raise it

  • Medium is the highest level the rules assign. High would need a second, independent demand source (search volume or marketplace installs), which is not connected.

The opportunity

All text in this section is generated by rule from the record. It is a starting point, not research.

Description
Developers are asking for Supabase access from AI agents more than the current supply of well-maintained tools would suggest.DER
Problem
Agents need to read from and act on Supabase. Only some of the existing tools are both documented and actively maintained.DER
Target users
Developers and individuals who use SupabaseHEU
Product form
MCP server (optionally bundled as a plugin with skills)HEU
Revenue model
Open source with paid hosting or supportHEU
Complexity
Low to mediumHEU
Competition level
HighDER
Subject
Supabase (integration)

Evidence for

4 row(s) from opportunity_evidence.

  • DemandMeasuredDERvalue 5,092

    5092 public GitHub issues contain the phrase "Supabase mcp" (checked 2026-11-21); that is the 89th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.

    Source

  • Growth (relative)MeasuredDERvalue 35

    35 products launched in the last 90 days versus 5 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.

  • FeasibilityHeuristicHEU

    Supabase has a public API (documentation linked).

    Source

  • DistributionMeasuredDERvalue 37

    37 of 47 tracked agent platforms document MCP support, so one MCP server can reach all of them.

    /platforms/

Evidence against

3 row(s) from opportunity_evidence.

  • Competition gapMeasuredDERvalue 29

    47 indexed products mention Supabase; 29 of them have a complete record and a repository pushed in the last 180 days.

    /integrations/supabase/

  • MonetisationHeuristicHEU

    Supabase is not primarily a paid business product. This is a rule of thumb, not revenue data.

  • Competition gapMeasuredDERvalue 1

    1 indexed product(s) are published under a namespace matching Supabase itself (Supabase). The gap score was reduced by 25 points for that.

    /integrations/supabase/

Existing products

All Supabase products

The most notable profiled products mentioning Supabase (up to 8). 47 indexed in total.

supabase-mcp-server

MCP serverby alexander-zuevHEU

837 GitHub starspushed 3mo agoApache-2.0

better-design

MCP serverby marvkrHEU

589 GitHub starspushed 26d agoMIT

supabase

Pluginby supabase-communitySRC

56 GitHub starspushed 1mo agolicence unknown

viberaven

MCP serverby ohad6kSRC

65 GitHub starspushed 1d agoMIT

Supabase

MCP serverby supabase.comSRC

pushed todayApache-2.0

PostgreSQL

MCP serverby antonorlovSRC

25 GitHub starspushed 2mo agoMIT

Where it could be distributed

All platforms

37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.

ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more

Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU

Data coverage

Indexed products
47DER
With a full profile
8+DER
Launches, last 90 days
35 vs 5 in the 90 beforeSRC
Demand measured
SRC
Segment calculated
Score calculated

Risks and counterarguments

  • The vendor may ship (or already ships) an official Supabase server, which usually becomes the default.
  • Issue mentions measure developer discussion, not willingness to pay.
  • 47 indexed products mention Supabase; 29 of them have a complete record and a repository pushed in the last 180 days.
  • Supabase is not primarily a paid business product. This is a rule of thumb, not revenue data.
  • 1 indexed product(s) are published under a namespace matching Supabase itself (Supabase). The gap score was reduced by 25 points for that.
  • The catalogue already holds a product for Supabase published by an account named after it: Supabase (supabase.com). That may be the vendor's own server; an account name is not proof.

Assumptions

What has to be true for the score to mean anything.

  • Mentions of "Supabase mcp" in GitHub issues reflect developers wanting Supabase access from agents.
  • Products that mention the integration in their description or package metadata are the competing supply; ones that do not name it are missed.
  • "Well-maintained" means data completeness ≥ 0.6 and a repository push in the last 180 days.
  • Percentiles compare this integration only with the other integrations tracked, not with the wider market.
  • A platform that documents MCP support can run any MCP server; no pairing has been tested.

How to verify this yourself

  1. Run the demand query on GitHub: https://github.com/search?q=%22Supabase%20mcp%22%20in%3Atitle%2Cbody%20is%3Aissue&type=issues. Compare the count with 5,092 on 2026-11-21; read a sample of issues to see whether they ask for agent access or merely mention it.
  2. Check the supply on the Supabase page and search the official MCP Registry and the vendor's own app directory for an official server.
  3. Download the record with all evidence: /api/dataset/opportunities.json.

All opportunities · Methodology · Report an error

Page data last updated .