The Supabase MCP runs as a **local stdio server** with full access to your Supabase project: - **Personal Access Token**: Your token provides administrative access to your Supabase account - **Full Database Access**: The AI can execute any SQL query, including writes and deletes - **Multi-Project Access**: Your token may have access to multiple Supabase projects - **Storage Access**: Files in your Storage buckets can be accessed and modified **Security best practices**: Use a dedicated Supabase account for development, never use production credentials during experimentation, enable Row Level Security (RLS) on sensitive tables, regularly rotate your access tokens, and consider using project-specific tokens when available.

To start using the Supabase MCP: 1. **Generate an access token**: Go to Supabase Dashboard → Account → Access Tokens → Generate New Token 2. **Copy your token**: Store it securely—it won't be shown again 3. **Configure the MCP**: Set the `SUPABASE_ACCESS_TOKEN` environment variable or pass via `--access-token` 4. **Add to your AI client**: Use `npx -y @supabase/mcp-server-supabase@latest --access-token YOUR_TOKEN` 5. **Start building**: Ask your AI to list tables or create a new database schema **Example**: "Create a users table with id, email, name, and created_at columns, then insert a sample user"