How sentry01/supabase-mcp-for-copilot works
Project type and purpose
• This is a middleware “Model Context Protocol (MCP) Supabase Server” written in Node.js.
• Purpose: act as a bridge between AI assistants (e.g., GitHub Copilot) and a Supabase database, exposing schema & safe query‐execution over an MCP-compatible server.
File structure
• Top‐level files:
• src/ – application code
– index.js: server bootstrap
– supabase-client.js: client factory
– schema-provider.js: fetch DB metadata
– query-handler.js: validate & run queries
– config.js: env-based configuration
– middleware/security.js: request-level checks
• sql/ – Supabase stored procedures (get_schema_information, etc.)
• .env.example, package.json, README.md, docs/guides/…
• Patterns & architecture:
• Single Node.js service following a modular design (client, provider, handler)
• Uses @modelcontextprotocol/server for MCP handshake
• RPC calls to Supabase functions for schema & query execution
README for additional insights
• Describes 3 main handlers: getSchema, getTableInfo, executeQuery.
• Highlights security via allowedQueryTypes, environment‐driven config, and RPC stored procedures.
Essential architectural elements
• Middleware/security module as a cross‐cutting concern on inbound requests.
• Configuration (dotenv) as a side input to supabase-client initialization.