MCP Multi-Project Setup Guide

​

Overview

​

Project Configuration

​

Current Projects

​

Configuration Options

​

Option 1: Hosted HTTP MCP Endpoints (Recommended)

{
  "mcpServers": {
    "supabase": {
      "url": "https://mcp.supabase.com/mcp?project_ref=rzfzikcargkoyhgqllap&read_only=true&features=database,debugging,development,docs,functions",
      "headers": {
        "Authorization": "Bearer ${env:SUPABASE_ACCESS_TOKEN}"
      }
    },
    "supabase-prod": {
      "url": "https://mcp.supabase.com/mcp?project_ref=anuwknikgsijbameytzr&read_only=true&features=database,debugging,development,docs,functions",
      "headers": {
        "Authorization": "Bearer ${env:SUPABASE_ACCESS_TOKEN}"
      }
    }
  }
}

• Use supabase tools for staging operations
• Use supabase-prod tools for production operations

​

Option 2: Environment-Based Project Switching (Single Entry)

{
  "mcpServers": {
    "supabase": {
      "url": "https://mcp.supabase.com/mcp?project_ref=${env:SUPABASE_PROJECT_REF}&read_only=true&features=database,debugging,development,docs,functions",
      "headers": {
        "Authorization": "Bearer ${env:SUPABASE_ACCESS_TOKEN}"
      }
    }
  }
}

# For staging
export SUPABASE_PROJECT_REF=rzfzikcargkoyhgqllap
# Restart Cursor

# For production
export SUPABASE_PROJECT_REF=anuwknikgsijbameytzr
# Restart Cursor

​

Option 3: Legacy stdio MCP Server (Compatibility)

​

Option 4: OAuth Client Per Environment (Enterprise)

1. Create OAuth Clients in Supabase Dashboard:
   • Go to Settings → API → OAuth Clients
   • Create mcp-staging client for staging project
   • Create mcp-production client for production project
2. Configure MCP with OAuth:
   {
     "mcpServers": {
       "supabase": {
         "command": "npx",
         "args": [
           "-y", "@supabase/mcp-server-supabase@latest",
           "--project-ref", "rzfzikcargkoyhgqllap",
           "--oauth-client-id", "${env:MCP_STAGING_CLIENT_ID}",
           "--oauth-client-secret", "${env:MCP_STAGING_CLIENT_SECRET}"
         ]
       }
     }
   }
   

​

Security Considerations

​

Access Token Management

• Personal Access Token: Generated from Supabase Dashboard → Account → Access Tokens
• Store in environment variable: SUPABASE_ACCESS_TOKEN
• Never commit access tokens to version control
• Rotate tokens regularly

​

Environment Isolation

​

Best Practices

1. Use staging by default for AI-assisted operations
2. Require explicit confirmation before production operations
3. Log all MCP operations for audit purposes
4. Rotate access tokens after team member departures

​

Available MCP Tools

​

Staging Project (mcp_supabase_*)

​

Production Project (mcp_supabase_prod_*)

• mcp_supabase_prod_execute_sql
• mcp_supabase_prod_list_tables
• etc.

​

Verification

​

Check Current Connection

-- Run via MCP to verify project
SELECT current_database(), current_user;

​

Verify Project Isolation

-- Check for seed data (should only exist in staging)
SELECT COUNT(*) FROM pf_organizations WHERE id::text LIKE '00000000-%';
-- Expected: 2 (staging), 0 (production)

​

Troubleshooting

​

MCP Connection Issues

1. Verify access token is set correctly
2. Check project reference matches intended environment
3. Restart Cursor after configuration changes
4. Check logs in Cursor Developer Tools

​

Wrong Project Connected

1. Stop immediately and assess damage
2. Check mcp_settings.json configuration
3. Verify environment variables
4. Revert any unintended changes

​

Related Documentation

• Supabase MCP Usage Guide
• Pre-Migration Test Plan (archived 2026-01 migration)
• AGENTS.md - Supabase MCP Usage section

​

Change Log