---
title: "supabase"
description: "Investigate Supabase-backed apps: schema, data access, RLS, and auth via Supabase's official PostgREST MCP server."
canonical: https://agentpluginsdirectory.com/plugins/supabase--hiai-gg
last-updated: 2026-09-22
---

# supabase
Investigate Supabase-backed apps: schema, data access, RLS, and auth via Supabase's official PostgREST MCP server.
- Slug: supabase--hiai-gg
- Publisher: HiAI
- Repository: https://github.com/HiAi-gg/agent-plugins
- Manifest: plugins/supabase/plugin.json
- Version: 0.0.2
- License: MIT
- Category (editorial): databases
- Skills: 4 (debug-auth, inspect-schema, investigate-supabase-app, review-rls)
- MCP servers: 1 (supabase)
- Stars: 1
- Repository created: 2026-08-08
- Repository last pushed: 2026-09-03
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/supabase--hiai-gg
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What supabase does, in the publisher's words

Investigate Supabase-backed apps: schema, data access, RLS, and auth, via Supabase's official PostgREST MCP server.

An Agent Plugin (spec 1.0.0).

A plugin that pairs Supabase's official @supabase/mcp-server-postgrest with skills for schema inspection, RLS review, auth debugging, and end-to-end investigation of a Supabase-backed app.

- First-party upstream: Supabase's own MCP server (repo supabase/mcp, Apache-2.0).
- Workflow value, not tool listing: the skills teach investigation order (schema → access → RLS → auth), not just what the tools do.
- Project-scoped, read-first: skills default to GET; writes require explicit intent.
- Server: supabase: stdio, npx -y @supabase/mcp-server-postgrest@0.1.1 --apiUrl --schema public (pinned, first-party).
- Skills: inspect-schema, review-rls, debug-auth, investigate-supabase-app.
- Node.js 18+ with npx.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/HiAi-gg/agent-plugins/HEAD/plugins/supabase/README.md

## Skills

- debug-auth: Debug Supabase authentication issues: signup, sign-in, session handling, and RLS access problems from the client perspective. Use when a user cannot sign in, sessions drop, or authenticated requests return 401/403 or empty results.
- inspect-schema: Inspect a Supabase/PostgREST schema through the official Supabase MCP: list tables, view columns and types, and understand the data model. Use when asked about the structure of a Supabase project's database.
- investigate-supabase-app: Investigate a Supabase-backed app end to end: schema, data access, RLS, and auth working together. Use when a feature is broken, data is missing, or the app behaves unexpectedly and the cause may be in the Supabase backend.
- review-rls: Review Row Level Security posture for a Supabase project: which tables have RLS enabled, which policies exist, and whether anon/authenticated access is over-permissive. Use when auditing a Supabase app's access control or before exposing a table via the API.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- supabase: transport: stdio; command: npx -y @supabase/mcp-server-postgrest@0.1.1 --apiUrl https://your-project-ref.supabase.co/rest/v1 --schema public

Read from the plugin's own mcp.json. Environment variable names only, never values.