We have configured the Supabase MCP (Model Context Protocol) server for Cursor. This allows the AI assistant to interact directly with your Supabase project.
The configuration file is located at .cursor/mcp.json:
{
"mcpServers": {
"supabase": {
"url": "https://mcp.supabase.com/mcp"
}
}
}To enable Figma tooling for agents, add the official Figma MCP server:
{
"mcpServers": {
"supabase": { "url": "https://mcp.supabase.com/mcp" },
"figma": {
"type": "http",
"url": "https://mcp.figma.com/mcp"
}
}
}Set your token in .env.local:
FIGMA_PERSONAL_ACCESS_TOKEN=your_figma_patThe Figma server exposes tools to fetch files, frames, components and assets via the Figma API.
supabase tool should now be available to the AIIf the automatic configuration doesn’t work, you can manually add the Supabase MCP server in Cursor settings:
supabaseSSE (Server-Sent Events)https://mcp.supabase.com/mcpFor local development with supabase start, you might need to use the local MCP URL provided by the CLI output.
We have consolidated all migration files into a single schema script for easier management.
docs/supabase/schema.sql)Contains the complete database schema, including:
Usage: Run this script in the Supabase SQL Editor to set up the entire database structure.
docs/supabase/seed.sql)Contains initial data for:
admin@ignitionstack.pro / admin123)Usage: Run this script after the schema script to populate the database with initial data.
docs/supabase/rollback.sql)WARNING: This script drops ALL tables and functions. Use only if you need to completely reset the database.