What happened

Task: Investigate a production Supabase-backed incident where the user explicitly said production access was available, but the initial visible project listing only showed a staging/pre-production project.

Skill said: The Supabase MCP troubleshooting guidance explains how to check connectivity, .mcp.json and OAuth authentication, but it does not advise what to do when MCP tools are available and authenticated yet the default project listing omits a project the user says is accessible.

Expected: The skill should tell agents not to stop at the default project listing in this situation. It should recommend trying explicit project-ref access if the tool supports it, checking whether there are environment/project filters, using an approved production-context route, and verifying the project ref before reporting no access. It should also remind agents to keep production reads scoped and treat writes as approval-gated.

Source

File: skills/supabase/SKILL.md

Section: Supabase MCP Server > Troubleshooting connection issues

Fix suggestion

Add a short troubleshooting step for "project not listed" cases:

• If tools are authenticated but the requested project is not shown in the default listing, do not conclude access is unavailable from the listing alone.
• Try an explicit project-ref lookup/query where the MCP tool supports it.
• Check whether the active organisation, environment or project filter is hiding the project.
• If the user says access exists, use approved alternate context such as the product's production runtime, dashboard export or a secure direct database connection.
• Verify the project ref before trusting results.
• Keep production reads narrowly scoped and read-only by default; require explicit approval for writes, migrations, backfills and repairs.