A
licenseNot graded
qualityD
maintenanceMCP server for Supabase, enabling database CRUD, storage management, auth administration, project management, edge functions, and secrets via 31 tools.
8 npm
MIT
MCP Supabase Server
by cloud9-labs
Related Servers
Alternatives to MCP Supabase Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that provides tools for interacting with Supabase databases, storage, and edge functions.45MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for self-hosted Supabase with RLS-aware PostgreSQL and PostgREST layers, enabling safe database introspection, SQL queries, and PostgREST access via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for exploring and querying Supabase databases with interactive React widgets for schema browsing, table viewing, and SQL execution.5,101,585 npm1MIT
- AlicenseAqualityCmaintenanceAn MCP server that provides deep schema introspection for Supabase/Postgres, exposing tables, columns, views, enums, RLS policies, functions, and more.133MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects to Supabase PostgreSQL databases, exposing table schemas as resources and providing tools for data analysis through SQL queries.1MIT
TDQS
B3.4/5.0
Scored across 12 tools
Disambiguation4/5
Most tools have clearly distinct resource+action targets (query vs insert vs update vs delete, table introspection vs storage ops). The one soft spot is three overlapping 'run arbitrary logic' tools — supabase_query, supabase_rpc, and supabase_execute_sql — where an agent may hesitate between SELECT-on-table, stored function, and raw SQL, though the descriptions do differentiate them.
Naming Consistency5/5
Every tool follows a strict supabase_<verb>_<noun> snake_case pattern (query, insert, update, delete, list_tables, get_table_schema, upload_file, list_files, delete_file, list_buckets). No deviations or mixed conventions.
Tool Count5/5
12 tools is well within the ideal range and each earns its place: three DB write ops, two read/introspection paths, one RPC/SQL path, and four storage ops. Nothing feels padded or missing at the count level.
Completeness4/5
Core coverage is strong: full row-level CRUD, schema introspection, RPC/raw SQL, and storage upload/list/delete/buckets. Minor gaps remain — no bucket creation, no file download/retrieval, no upsert, and no auth/user or policy management — but these are workable around or out of the server's stated scope.
Maintenance
ActivityInactive
ResponsivenessNo issues