Quick Configuration
Choose the setup that matches your environment.
Before You Start
- Confirm you have the account, endpoint, or API key required for Supabase.
- Start with minimum scopes and read-only access where possible.
- Keep secrets in environment variables instead of hardcoding them in JSON.
Hosted / Remote
JSON Hosted Config json
{
"supabase": {
"url": "https://YOUR_SUPABASE_MCP_ENDPOINT"
}
}Local CLI (npx)
JSON Local Config json
{
"supabase": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://YOUR_SUPABASE_MCP_ENDPOINT"],
"env": {
"SUPABASE_API_KEY": "YOUR_SUPABASE_API_KEY"
}
}
}Common Pitfalls & Fixes
- â ī¸ Watch out: Service role keys vs anon keys, RLS policies, and environment separation.
- đ Always store API keys in environment variables, never hardcode them in JSON.
- đĄī¸ Start with read-only scopes if available to verify connection safely.
Example Prompts
Once connected, try these prompts to test capabilities:
- List tables in the public schema and describe the most important ones.
- Check RLS policies on the users table and explain the access rules.
- Draft a safe migration plan for adding a new column with minimal downtime.
Verification Checklist
- Run 1-2 real prompts to confirm Supabase returns usable data.
- Check that error messages are clear enough for troubleshooting.
- Document the required scopes, dependencies, and env vars for future reuse.