Supabase is an open source Firebase alternative, providing a PostgreSQL database, authentication, instant APIs, realtime subscriptions, and storage.
Why this server?
Fronts the Supabase MCP server, routing requests to its project, database, and table tools when Supabase resources are involved.
Why this server?
Provides persistent cloud storage and semantic search for GitMem's memory, leveraging Supabase as the backend for the Pro tier.
Why this server?
Provides optional authentication and user session management for the runtime.
Why this server?
Provides buyer account, audit, and compliance tools authenticated via Supabase JWTs.
Why this server?
Provides access to live Supabase SDK documentation, including full-text search, package registry lookup, and open GitHub issues.
Why this server?
Optional persistent backend for storing workspaces and knowledge entries in Supabase, with automatic fallback to local file storage.
Why this server?
Read-only security audit of a Supabase project, using a dedicated read-only role plus the project's REST URL and anon key. Provides four read-only tools, an `audit` prompt, and the anti-pattern catalog as resources to inspect RLS status, policies, views, exposed SECURITY DEFINER functions, grants and API exposure, then report scored findings (e.g. RLS disabled, `USING (true)`, service-role key in frontend, views bypassing RLS, user_metadata in policies, mass assignment, public buckets) with exact fix SQL.
Why this server?
Allows searching for Supabase, casting trust reviews, and checking known problems on the NaN Mesh trust network.
Why this server?
Checks Supabase projects for missing Row Level Security, insecure policies, public storage buckets, exposed service_role keys, and publicly readable tables.
